summaryrefslogtreecommitdiff
path: root/opcodes
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2013-10-07 11:13:08 +0000
committerPedro Alves <palves@redhat.com>2013-10-07 11:13:08 +0000
commit5c5ea68c9e10fbc507a7ce995a85246c26032c8c (patch)
tree1a284b1a92ac4134e3d79e3abce6edecb13e112f /opcodes
parentb2720bc57b6ccee7157e7f7dc23cf310cf066677 (diff)
downloadgdb-5c5ea68c9e10fbc507a7ce995a85246c26032c8c.tar.gz
[DOC] Mention what happens when the thread of a thread-specific breakpoint disappears.
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.
Diffstat (limited to 'opcodes')
0 files changed, 0 insertions, 0 deletions