Red Hat ENTERPRISE LINUX 4 - DEVELOPER TOOLS GUIDE, Manual

Page: 41 / 410

Chapter 6. Running Programs Under gdb 31
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 HP-UX systems:
For debugging purposes, gdb associates its own thread number--a small integer assigned in thread-
creation order--with each thread in your program.
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 HP-UX, you
see
[New thread 2 (system thread 26594)]
when gdb notices a new thread.
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 system thread 26607 worker (wptr=0x7b09c318 "@") \
at quicksort.c:137
2 system thread 26606 0x7b0030d8 in __ksleep () \
from /usr/lib/libc.2