diff options
Diffstat (limited to 'gdb')
| -rw-r--r-- | gdb/doc/ChangeLog | 6 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 18 |
2 files changed, 24 insertions, 0 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 89254a99394..5141b3ce0e3 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,9 @@ +2013-10-07 Pedro Alves <palves@redhat.com> + + PR breakpoints/11568 + * gdb.texinfo (Thread-Specific Breakpoints): Mention what happens + when the thread is removed from the thread list. + 2013-10-06 Sergio Durigan Junior <sergiodj@redhat.com> * gdb.texinfo (Convenience Variables): Document $_exitsignal. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 7ec91d85925..e196658660b 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -5864,6 +5864,24 @@ after the breakpoint condition, like this: @end table +Thread-specific breakpoints are automatically deleted when +@value{GDBN} detects the corresponding thread is no longer in the +thread list. For example: + +@smallexample +(@value{GDBP}) c +Thread-specific breakpoint 3 deleted - thread 28 no longer in the thread list. +@end smallexample + +There are several ways for a thread to disappear, such as a regular +thread exit, but also when you detach from the process with the +@code{detach} command (@pxref{Attach, ,Debugging an Already-running +Process}), or if @value{GDBN} loses the remote connection +(@pxref{Remote Debugging}), etc. Note that with some targets, +@value{GDBN} is only able to detect a thread has exited when the user +explictly asks for the thread list with the @code{info threads} +command. + @node Interrupted System Calls @subsection Interrupted System Calls |