diff options
| author | Andrew Burgess <andrew.burgess@embecosm.com> | 2021-08-10 11:20:44 +0100 |
|---|---|---|
| committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2021-09-07 12:44:08 +0100 |
| commit | 611841bb1afc689becfab6dd490e1799aabf547d (patch) | |
| tree | 9408d2caedec7fd55131479e3bb2964ad7382515 /gdb/target.c | |
| parent | 9dc2f26777b07f9e5aa3220f7a680987ef79e75e (diff) | |
| download | gdb-611841bb1afc689becfab6dd490e1799aabf547d.zip gdb-611841bb1afc689becfab6dd490e1799aabf547d.tar.gz gdb-611841bb1afc689becfab6dd490e1799aabf547d.tar.bz2 | |
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.
Diffstat (limited to 'gdb/target.c')
| -rw-r--r-- | gdb/target.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/target.c b/gdb/target.c index ae2d659..d1c1bf5 100644 --- a/gdb/target.c +++ b/gdb/target.c @@ -3815,7 +3815,7 @@ target_pass_ctrlc (void) { /* A thread can be THREAD_STOPPED and executing, while running an infcall. */ - if (thr->state == THREAD_RUNNING || thr->executing) + if (thr->state == THREAD_RUNNING || thr->executing ()) { /* We can get here quite deep in target layers. Avoid switching thread context or anything that would |