From: Keith Seitz <keiths@redhat.com>
To: <gdb@sources.redhat.com>
Subject: [RFC] Breakpoint events: revisited
Date: Tue, 18 Jun 2002 11:00:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0206181056060.6521-100000@makita.cygnus.com> (raw)
Hi,
Ok, I hate to beat a dead horse, BUT...
A long time ago, I proposed eradicating UI notification for internal
breakpoints. It was argued at the time that they should be available to UI
writers wishing to expose these things to some class of users. Fair
enough.
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?
I have a patch which adds _all_ of them, and removes the stupid creation
event from mention (removing the FIXME at the same time).
Keith
next reply other threads:[~2002-06-18 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 11:00 Keith Seitz [this message]
2002-06-18 22:27 ` Eli Zaretskii
2002-06-19 7:45 ` Andrew Cagney
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=Pine.GSO.4.33.0206181056060.6521-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=gdb@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