From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Keith Seitz <keiths@redhat.com>, gdb@sources.redhat.com
Subject: Re: [RFC] Breakpoint events: revisited
Date: Wed, 19 Jun 2002 07:45:00 -0000 [thread overview]
Message-ID: <3D1098FA.4050201@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020619082357.27660G-100000@is>
> On Tue, 18 Jun 2002, Keith Seitz wrote:
>
>
>> Well, while working on converting MI over to use events instead of hooks,
>> I noticed that GDB currently only notifies the UI about some internal
>> breakpoints, not all of them.
>>
>> So (beat, beat):
>>
>> Do we still want to expose _all_ internal breakpoints to UIs via
>> breakpoint events, or just some of them? Which ones?
>
>
> My $0.02 would be that we should at least be consistent: either expose
> all of them, or none.
Yes.
>> I have a patch which adds _all_ of them, and removes the stupid creation
>> event from mention (removing the FIXME at the same time).
>
>
> I tend to agree with this.
>
Andrew
prev parent reply other threads:[~2002-06-19 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 11:00 Keith Seitz
2002-06-18 22:27 ` Eli Zaretskii
2002-06-19 7:45 ` Andrew Cagney [this message]
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=3D1098FA.4050201@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=keiths@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