diff options
author | Eli Zaretskii <eliz@gnu.org> | 2006-01-21 21:14:10 +0000 |
---|---|---|
committer | Eli Zaretskii <eliz@gnu.org> | 2006-01-21 21:14:10 +0000 |
commit | 839c27b7cf6bb1e49ed824ea028e07bdd8ba36bf (patch) | |
tree | 3a8548c022ee1e35b812969422820855f2d312b3 | |
parent | 878d91936fddadb1fa647386134bf65b0712ea08 (diff) | |
download | fsf-binutils-gdb-839c27b7cf6bb1e49ed824ea028e07bdd8ba36bf.zip fsf-binutils-gdb-839c27b7cf6bb1e49ed824ea028e07bdd8ba36bf.tar.gz fsf-binutils-gdb-839c27b7cf6bb1e49ed824ea028e07bdd8ba36bf.tar.bz2 |
(Backtrace): Describe how to get backtrace of all the threads in a
multi-threaded program.
(Threads): The threadno argument of "thread apply" can be a range of numbers.
-rw-r--r-- | gdb/doc/ChangeLog | 7 | ||||
-rw-r--r-- | gdb/doc/gdb.texinfo | 24 |
2 files changed, 24 insertions, 7 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index c48c8f0..d9aac34 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,10 @@ +2006-01-21 Eli Zaretskii <eliz@gnu.org> + + * gdb.texinfo (Backtrace): Describe how to get backtrace of all + the threads in a multi-threaded program. + (Threads): The threadno argument of "thread apply" can be a range + of numbers. + 2006-01-18 Jim Blandy <jimb@redhat.com> * gdbint.texinfo (Coding): Add entry for -Wno-pointer-sign to list diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 9160094..c17520a 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -2424,13 +2424,14 @@ threads. @kindex thread apply @cindex apply command to several threads -@item thread apply [@var{threadno}] [@var{all}] @var{args} -The @code{thread apply} command allows you to apply a command to one or -more threads. Specify the numbers of the threads that you want affected -with the command argument @var{threadno}. @var{threadno} is the internal -@value{GDBN} thread number, as shown in the first field of the @samp{info -threads} display. To apply a command to all threads, use -@code{thread apply all} @var{args}. +@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 +@var{threadno}. It can be a single thread number, one of the numbers +shown in the first field of the @samp{info threads} display; or it +could be a range of thread numbers, as in @code{2-4}. To apply a +command to all threads, type @kbd{thread apply all @var{command}}. @end table @cindex automatic thread selection @@ -4461,6 +4462,15 @@ Print the values of the local variables also. The names @code{where} and @code{info stack} (abbreviated @code{info s}) are additional aliases for @code{backtrace}. +@cindex multiple threads, backtrace +In a multi-threaded program, @value{GDBN} by default shows the +backtrace only for the current thread. To display the backtrace for +several or all of the threads, use the command @code{thread apply} +(@pxref{Threads, thread apply}). For example, if you type @kbd{thread +apply all backtrace}, @value{GDBN} will display the backtrace for all +the threads; this is handy when you debug a core dump of a +multi-threaded program. + Each line in the backtrace shows the frame number and the function name. The program counter value is also shown---unless you use @code{set print address off}. The backtrace also shows the source file name and |