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 <alves dot ped at gmail dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org
- Date: Fri, 04 Oct 2013 18:54:46 +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>
On 10/04/2013 06:48 PM, Eli Zaretskii wrote:
>> From: Pedro Alves <palves@redhat.com>
>> Date: Fri, 4 Oct 2013 16:01:36 +0100
>>
>> 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?
>
> Yes, thanks. One nit, though:
>
>> +Thread-specific breakpoints are automatically deleted when
>> +@value{GDBN} detects the corresponding thread is gone.
> ^^^^^^^^^^^^^^
> I'd say "thread exits" instead.
That was on purpose. It's what GDB says too. That's because
there are other ways for a thread to disappear other than
a regular thread exit, such as "detach", "disconnect"
or gdb losing the remote connection, etc. The thread hasn't
really exited in those cases.
--
Pedro Alves