thread identifier whose form varies depending on the particular system. For example, on LynxOS, you might see
[New process 35 thread 27]
when GDB notices a new thread. In contrast, on an SGI system, the systag is simply something like 'process 368', with no further qualifier.
For debugging purposes, GDB associates its own thread number―always a single integer―with each thread in your program.
info threads Display a summary of all threads currently in your program. GDB displays for each thread (in this order):
1.the thread number assigned by GDB
2.the target system's thread identifier (systag)
3.the current stack frame summary for that thread
An asterisk '*' to the left of the GDB thread number indicates the current thread.
For example,
((gdb)) info threads
3 process 35 thread 27 0x34e5 in sigpause ()
2 process 35 thread 23 0x34e5 in sigpause ()
* 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8)
at threadtest.c:68
On
For debugging purposes, GDB associates its own thread number―a small integer assigned in
Whenever GDB detects a new thread in your program, it displays both GDB's thread number and the target system's identification for the thread with a message in the form '[New systag]'. systag is a thread identifier whose form varies depending on the particular system. For example, on
[New thread 2 (system thread 26594)]
when GDB notices a new thread.
On
set threadverbose on Enable the output of informational messages regarding thread creation. The default setting is on. You can set it to off to stop displaying of messages.
set threadverbose off Disable the output of informational messages regarding thread creation. The default setting is on. You can set it to on to display messages.
4.9 Debugging programs with multiple threads | 47 |