From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't give spurious warnings when using thread specific breakpoints
Date: Wed, 11 Oct 2006 20:45:00 -0000 [thread overview]
Message-ID: <20061011204525.GA9622@nevyn.them.org> (raw)
In-Reply-To: <452D0385.6010103@st.com>
On Wed, Oct 11, 2006 at 03:45:25PM +0100, Andrew STUBBS wrote:
> Daniel Jacobowitz wrote:
> >(gdb) b main if 1
> >Breakpoint 1 at 0x439ee0
> >(gdb) b main if 2
> >Note: breakpoint 1 also set at pc 0x439ee0.
> >Breakpoint 2 at 0x439ee0
> >
> >If that's right, why is similar for threads wrong? That's just a
> >different condition. And the wording is such that it's perfectly
> >correct.
>
> Maybe that is wrong too, but, as you say, it isn't lying.
>
> I would argue that a breakpoint in another thread is not in the same
> location (unlike a condition). The similarity of the PC might be
> considered an accident of the implementation, perhaps.
>
> It's also easy to tell that the thread is different, while comparing
> conditions makes no sense (although checking for the presence of
> conditions might).
This does make a little sense to me. Anyone think there's value in keeping
the note for breakpoints in different threads?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-11 20:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 13:44 Andrew STUBBS
2006-10-11 13:55 ` Daniel Jacobowitz
2006-10-11 14:46 ` Andrew STUBBS
2006-10-11 20:45 ` Daniel Jacobowitz [this message]
2006-10-11 22:12 ` Mark Kettenis
2006-10-11 22:14 ` Joel Brobecker
2006-10-18 12:01 ` Andrew STUBBS
2006-10-18 14:14 ` Daniel Jacobowitz
2006-10-18 15:12 ` Andrew STUBBS
2006-10-18 19:47 ` Eli Zaretskii
2006-10-18 20:21 ` Andreas Schwab
2006-10-19 4:17 ` Eli Zaretskii
2006-10-19 9:47 ` Andrew STUBBS
2006-10-20 6:10 ` Eli Zaretskii
2006-10-20 14:29 ` Daniel Jacobowitz
2006-10-20 17:42 ` Eli Zaretskii
2006-10-20 17:47 ` Daniel Jacobowitz
2006-10-20 18:03 ` Eli Zaretskii
2006-10-20 18:07 ` Daniel Jacobowitz
2006-10-20 18:11 ` Eli Zaretskii
2006-10-19 13:28 ` Daniel Jacobowitz
2006-10-19 15:59 ` Andrew STUBBS
2006-10-18 19:22 ` Eli Zaretskii
2006-10-11 22:06 ` Mark Kettenis
2006-10-12 10:45 ` Andrew STUBBS
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=20061011204525.GA9622@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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