From f6e29b6ec0a4fd410ddaaddacf045c4cb4e890f2 Mon Sep 17 00:00:00 2001 From: Yao Qi Date: Wed, 18 Jun 2014 22:00:54 +0800 Subject: [PATCH] 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 * gdbthread.h (struct thread_info) : Change its type to 'enum thread_state'. Update comments. --- gdb/ChangeLog | 5 +++++ gdb/gdbthread.h | 14 ++++++-------- 2 files changed, 11 insertions(+), 8 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 850b26754bf..36a74be8452 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2014-06-19 Yao Qi + + * gdbthread.h (struct thread_info) : Change its type to + 'enum thread_state'. Update comments. + 2014-06-19 Pedro Alves * gdbthread.h (ALL_THREADS): Delete. diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h index 64e37c3cdc7..ca529831aaa 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 -- 2.30.2