diff options
| -rw-r--r-- | gdb/doc/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 73 |
2 files changed, 65 insertions, 13 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 594baae..a64db4c 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,8 +1,3 @@ -2011-01-11 Tom Tromey <tromey@redhat.com> - - * gdb.texinfo (Threads): Remove duplicate text. Update examples. - Fix "thread apply" text. - 2011-01-11 Sergio Durigan Junior <sergiodj@linux.vnet.ibm.com> Thiago Jung Bauermann <bauerman@br.ibm.com> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index b86e8d2..8e42913 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -2731,13 +2731,70 @@ For example, @smallexample (@value{GDBP}) info threads - Id Target Id Frame - 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) + 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 @end smallexample +On HP-UX systems: + +@cindex debugging multithreaded programs (on HP-UX) +@cindex thread identifier (GDB), on HP-UX +For debugging purposes, @value{GDBN} associates its own thread +number---a small integer assigned in thread-creation order---with each +thread in your program. + +@cindex @code{New} @var{systag} message, on HP-UX +@cindex thread identifier (system), on HP-UX +@c FIXME-implementors!! It would be more helpful if the [New...] message +@c included GDB's numeric thread handle, so you could just go to that +@c thread without first checking `info threads'. +Whenever @value{GDBN} detects a new thread in your program, it displays +both @value{GDBN}'s thread number and the target system's identification for the thread with a message in the +form @samp{[New @var{systag}]}. @var{systag} is a thread identifier +whose form varies depending on the particular system. For example, on +HP-UX, you see + +@smallexample +[New thread 2 (system thread 26594)] +@end smallexample + +@noindent +when @value{GDBN} notices a new thread. + +@table @code +@kindex info threads (HP-UX) +@item info threads +Display a summary of all threads currently in your +program. @value{GDBN} displays for each thread (in this order): + +@enumerate +@item the thread number assigned by @value{GDBN} + +@item the target system's thread identifier (@var{systag}) + +@item the current stack frame summary for that thread +@end enumerate + +@noindent +An asterisk @samp{*} to the left of the @value{GDBN} thread number +indicates the current thread. + +For example, +@end table +@c end table here to get a little more width for example + +@smallexample +(@value{GDBP}) 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 + 1 system thread 27905 0x7b003498 in _brk () \@* + from /usr/lib/libc.2 +@end smallexample + On Solaris, you can display more information about user threads with a Solaris-specific command: @@ -2758,10 +2815,10 @@ shown in the first field of the @samp{info threads} display. you selected, and its current stack frame summary: @smallexample +@c FIXME!! This example made up; find a @value{GDBN} w/threads and get real one (@value{GDBP}) thread 2 -[Switching to thread 2 (Thread 0xb7fdab70 (LWP 12747))] -#0 some_function (ignore=0x0) at example.c:8 -8 printf ("hello\n"); +[Switching to process 35 thread 23] +0x34e5 in sigpause () @end smallexample @noindent @@ -2778,7 +2835,7 @@ information on convenience variables. @kindex thread apply @cindex apply command to several threads -@item thread apply [@var{threadno} | all] @var{command} +@item thread apply [@var{threadno}] [@var{all}] @var{command} The @code{thread apply} command allows you to apply the named @var{command} to one or more threads. Specify the numbers of the threads that you want affected with the command argument |