From: Matt Rice <ratmice@gmail.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Simplify MI breakpoint setting
Date: Tue, 08 Sep 2009 07:59:00 -0000 [thread overview]
Message-ID: <8ba6bed40909080059q5ff75456j493580304ec6f8ef@mail.gmail.com> (raw)
In-Reply-To: <200909080920.27288.vladimir@codesourcery.com>
On Mon, Sep 7, 2009 at 10:20 PM, Vladimir Prus<vladimir@codesourcery.com> wrote:
> On Tuesday 08 September 2009 Matt Rice wrote:
<snip>
>>
>> I don't like how break_command_really looks for the symbol first, then
>> if it fails to find one and
>> pending breakpoints are enabled it will set a pending breakpoint, I
>> think it might sometimes make sense
>> to set a pending breakpoint even though there may be a match.
>
> I am missing something. Pending breakpoint, by definition, is a breakpoint
> that has zero locations. And breakpoint can have zero locations if and only
> if we have failed to find any location that corresponds to the string
> that user has specified. Therefore, pending breakpoint for a found symbol
> or line seems just impossible.
>
I was only speaking about the behaviour of pending breakpoints where
they accumulate a location
when a location matching the user specified string is loaded in the
future, which seems useful to me regardless of it
having a location when using languages where it is possible for the
user specified string to match multiple locations.
But yes it appears that would not be a pending breakpoint by the
definition given by you and manual.
next prev parent reply other threads:[~2009-09-08 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 7:13 Vladimir Prus
2009-08-07 18:52 ` Tom Tromey
2009-08-24 10:55 ` Vladimir Prus
2009-08-31 23:35 ` Tom Tromey
2009-09-01 5:16 ` Vladimir Prus
2009-09-07 23:00 ` Matt Rice
2009-09-08 5:20 ` Vladimir Prus
2009-09-08 7:59 ` Matt Rice [this message]
2009-09-08 8:15 ` Vladimir Prus
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=8ba6bed40909080059q5ff75456j493580304ec6f8ef@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.com \
--cc=vladimir@codesourcery.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