From: Michael Snyder <msnyder@redhat.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Disable thread specific breakpoints when thread dies
Date: Fri, 13 Jan 2006 04:19:00 -0000 [thread overview]
Message-ID: <43C729FA.2020500@redhat.com> (raw)
In-Reply-To: <43C6825C.9020909@st.com>
Daniel,
valid_thread_id wouldn't be safe, because thread ids might be re-used.
This implementation looks fine to me...
Michael
Andrew STUBBS wrote:
> Ping.
>
> Since valid_thread_id did not work am I OK to commit this one. It has
> been on hold since mid Novemeber.
>
> Thanks
>
> Andrew
>
> Andrew Stubbs wrote:
>
>> Daniel Jacobowitz wrote:
>>
>>> On Wed, Nov 16, 2005 at 02:52:17PM +0000, Andrew STUBBS wrote:
>>>
>>>> + /* There is no point inserting thread-specific breakpoints if
>>>> the
>>>> + thread no longer exists. */
>>>> + if (b->owner->thread != -1
>>>> + && !target_thread_alive(thread_id_to_pid(b->owner->thread)))
>>>> + continue;
>>>
>>>
>>>
>>>
>>> You shouldn't need to use the target method here. Does valid_thread_id
>>> work?
>>>
>>> Also, please remember the space before opening parentheses.
>>
>>
>>
>> The thread still seems to have a valid ID after it has died. You can
>> even do 'b 8 t 4' after the program has exited. It does give an error
>> for threads which never existed though.
>>
>> Here is the patch again with the spaces fixed.
>>
>> Andrew
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> 2005-11-17 Andrew Stubbs <andrew.stubbs@st.com>
>>
>> * breakpoint.c (insert_breakpoints): Check that a thread exists
>> before inserting thread specific breakpoints.
>>
>> Index: src/gdb/breakpoint.c
>> ===================================================================
>> --- src.orig/gdb/breakpoint.c 2005-11-17 15:47:04.000000000 +0000
>> +++ src/gdb/breakpoint.c 2005-11-17 15:47:42.000000000 +0000
>> @@ -1142,6 +1142,12 @@ insert_breakpoints (void)
>> if (!breakpoint_enabled (b->owner))
>> continue;
>>
>> + /* There is no point inserting thread-specific breakpoints if the
>> + thread no longer exists. */
>> + if (b->owner->thread != -1
>> + && !target_thread_alive (thread_id_to_pid (b->owner->thread)))
>> + continue;
>> +
>> /* FIXME drow/2003-10-07: This code should be pushed elsewhere
>> when
>> hardware watchpoints are split into multiple loc breakpoints. */
>> if ((b->loc_type == bp_loc_hardware_watchpoint
>
>
>
next prev parent reply other threads:[~2006-01-13 4:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 19:06 Andrew STUBBS
2005-11-13 21:13 ` Daniel Jacobowitz
2005-11-14 16:34 ` Andrew STUBBS
2005-11-14 17:11 ` Daniel Jacobowitz
2005-11-15 18:55 ` Andrew STUBBS
2005-11-16 16:23 ` Andrew STUBBS
2005-11-17 4:22 ` Daniel Jacobowitz
2005-11-17 16:34 ` Andrew STUBBS
2006-01-12 16:25 ` Andrew STUBBS
2006-01-13 4:19 ` Michael Snyder [this message]
2006-01-13 4:31 ` Daniel Jacobowitz
2006-01-12 16:27 ` Daniel Jacobowitz
2006-01-13 17:35 ` Andrew STUBBS
2006-01-13 20:11 ` Mark Kettenis
2006-01-14 15:46 ` Daniel Jacobowitz
2006-01-14 15:56 ` Mark Kettenis
2006-01-14 16:06 ` Daniel Jacobowitz
2006-01-16 12:57 ` Andrew STUBBS
2006-01-16 16:19 ` Andrew STUBBS
2006-01-20 14:56 ` Andrew STUBBS
2006-01-20 15:00 ` Daniel Jacobowitz
2006-01-20 22:41 ` Daniel Jacobowitz
2006-02-02 2:30 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C729FA.2020500@redhat.com \
--to=msnyder@redhat.com \
--cc=andrew.stubbs@st.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox