This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PATCH] [DOC] Mention what happens when the thread of a thread-specific breakpoint is gone.
- From: Pedro Alves <palves at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Fri, 4 Oct 2013 16:01:36 +0100
- Subject: [PATCH] [DOC] Mention what happens when the thread of a thread-specific breakpoint is gone.
- Authentication-results: sourceware.org; auth=none
We recently made GDB auto-delete thread-specific breakpoints when the
corresponding thread is gone, but we haven't mentioned it in the manual.
OK?
gdb/
2013-10-04 Pedro Alves <palves@redhat.com>
PR breakpoints/11568
* gdb.texinfo (Thread-Specific Breakpoints): Mention what happens
when the thread is gone.
---
gdb/doc/gdb.texinfo | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index a68556b..97b0aff 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -5864,6 +5864,14 @@ after the breakpoint condition, like this:
@end table
+Thread-specific breakpoints are automatically deleted when
+@value{GDBN} detects the corresponding thread is gone. For example:
+
+@smallexample
+(@value{GDBP}) c
+Thread-specific breakpoint 3 deleted - thread 28 is gone.
+@end smallexample
+
@node Interrupted System Calls
@subsection Interrupted System Calls
--
1.7.11.7