aboutsummaryrefslogtreecommitdiff
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
commitf4fb82a1276909f3572086b5edf14760a75e7dec (patch)
tree58e29f06286f4fd6c513f42b9d83581f94b28a68 /opcodes
parent46ecd52745f46247ab5e2c3b6ccda8bc3458242d (diff)
downloadgdb-f4fb82a1276909f3572086b5edf14760a75e7dec.zip
gdb-f4fb82a1276909f3572086b5edf14760a75e7dec.tar.gz
gdb-f4fb82a1276909f3572086b5edf14760a75e7dec.tar.bz2
[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