aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdbthread.h
diff options
context:
space:
mode:
authorYao Qi <yao@codesourcery.com>2014-06-18 22:00:54 +0800
committerYao Qi <yao@codesourcery.com>2014-06-19 20:14:43 +0800
commitf6e29b6ec0a4fd410ddaaddacf045c4cb4e890f2 (patch)
tree791720c012bb7598e66c727362fe650cee348c6f /gdb/gdbthread.h
parent034f788c5ec1e5b20fae3b6efc7fe961631e014d (diff)
Use enum thread_state
This patch is to change field state's type to 'enum thread_state', and replace RUNNING with THREAD_RUNNING and STOPPED with THREAD_STOPPED respectively in comments. gdb: 2014-06-19 Yao Qi <yao@codesourcery.com> * gdbthread.h (struct thread_info) <state>: Change its type to 'enum thread_state'. Update comments.
Diffstat (limited to 'gdb/gdbthread.h')
-rw-r--r--gdb/gdbthread.h14
1 files changed, 6 insertions, 8 deletions
diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h
index 64e37c3cdc..ca529831aa 100644
--- a/gdb/gdbthread.h
+++ b/gdb/gdbthread.h
@@ -157,14 +157,12 @@ struct thread_info
thread is off and running. */
int executing;
- /* Frontend view of the thread state. Note that the RUNNING/STOPPED
- states are different from EXECUTING. When the thread is stopped
- internally while handling an internal event, like a software
- single-step breakpoint, EXECUTING will be false, but running will
- still be true. As a possible future extension, this could turn
- into enum { stopped, exited, stepping, finishing, until(ling),
- running ... } */
- int state;
+ /* Frontend view of the thread state. Note that the THREAD_RUNNING/
+ THREAD_STOPPED states are different from EXECUTING. When the
+ thread is stopped internally while handling an internal event,
+ like a software single-step breakpoint, EXECUTING will be false,
+ but STATE will still be THREAD_RUNNING. */
+ enum thread_state state;
/* If this is > 0, then it means there's code out there that relies
on this thread being listed. Don't delete it from the lists even