gdb: make thread_info::executing private
authorAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 10 Aug 2021 10:20:44 +0000 (11:20 +0100)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 7 Sep 2021 11:44:08 +0000 (12:44 +0100)
commit611841bb1afc689becfab6dd490e1799aabf547d
tree9408d2caedec7fd55131479e3bb2964ad7382515
parent9dc2f26777b07f9e5aa3220f7a680987ef79e75e
gdb: make thread_info::executing private

Rename thread_info::executing to thread_info::m_executing, and make it
private.  Add a new get/set member functions, and convert GDB to make
use of these.

The only real change of interest in this patch is in thread.c where I
have deleted the helper function set_executing_thread, and now just
use the new set function thread_info::set_executing.  However, the old
helper function set_executing_thread included some code to reset the
thread's stop_pc, so I moved this code into the new function
thread_info::set_executing.  However, I don't believe there is
anywhere that this results in a change of behaviour, previously the
executing flag was always set true through a call to
set_executing_thread anyway.
gdb/breakpoint.c
gdb/frame.c
gdb/gdbthread.h
gdb/infcmd.c
gdb/inflow.c
gdb/infrun.c
gdb/linux-nat.c
gdb/linux-thread-db.c
gdb/record-btrace.c
gdb/target.c
gdb/thread.c