This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] [DOC] Mention what happens when the thread of a thread-specific breakpoint is gone.
- From: Pedro Alves <palves at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 07 Oct 2013 12:14:20 +0100
- Subject: Re: [PATCH] [DOC] Mention what happens when the thread of a thread-specific breakpoint is gone.
- Authentication-results: sourceware.org; auth=none
- References: <1380898896-16767-1-git-send-email-palves at redhat dot com> <83y569apvb dot fsf at gnu dot org> <524F00E6 dot 9010104 at gmail dot com> <524F01E4 dot 7050902 at redhat dot com> <524F086C dot 3030908 at redhat dot com> <83siwgc07r dot fsf at gnu dot org>
On 10/04/2013 08:20 PM, Eli Zaretskii wrote:
>> From: Pedro Alves <palves@redhat.com>
>> What about this? I'm now saying "no longer in the thread list"
>> instead of "is gone".
>
> This is good, thanks.
Thanks. Applied, with the small example adjusted to gdb's new output.
-------------
[DOC] Mention what happens when the thread of a thread-specific breakpoint is gone.
We recently made GDB auto-delete thread-specific breakpoints when the
corresponding thread is removed from the thread list, but we hadn't
mentioned it in the manual.
gdb/
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.
---
gdb/doc/gdb.texinfo | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 7ec91d8..e196658 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