From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: Remove gdb-events
Date: Mon, 21 Jul 2008 17:13:00 -0000 [thread overview]
Message-ID: <g62g35$l1h$1@ger.gmane.org> (raw)
In-Reply-To: <m3tzeubpw5.fsf@fleche.redhat.com>
Tom Tromey wrote:
> My understanding is that the gdb "events" mechanism is deprecated in
> favor of using observers.
>
> This patch removes events and adds observers where needed.
>
> Most of this patch is straightforward. There are a few odd pieces:
>
> * Removing the call to clear_gdb_event_hooks. In theory I think this
> could confuse some caller. However, in practice I think it is
> probably nothing to worry about.
>
> * The architecture_changed observer is needed for gdbtk, but the only
> place where this is notified is deprecated. Since my goal here is
> to remove events, I think this is probably fine. It certainly
> doesn't seem any worse.
>
> * MI installs a new set of event handlers, does some work, then
> uninstalls them. Instead of trying to replicate this behavior --
> say by deinstalling other observers -- I just made the MI observer
> conditional on a global flag, which is set and reset at the
> appropriate points.
I think it would have been nicer to install observers in mi_interpreter_init,
but it's not critical matter. The mi_can_breakpoint_notify will probably
remain forever, so that we report breakpoints differently when they are created
during -break-insert and when they are created by other commands -- the
former needs to report new breakpoint as part of ^done reply, and the latter
has to use notification.
I don't have any objections to the MI part of this change -- thanks for asking
for an opinion!
- Volodya
next prev parent reply other threads:[~2008-07-21 17:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 0:16 Tom Tromey
2008-07-13 3:26 ` Stan Shebs
2008-07-13 21:56 ` Tom Tromey
2008-08-01 16:20 ` Tom Tromey
2008-08-01 16:33 ` Subdir ChangeLogs (was Re: RFA: Remove gdb-events) Stan Shebs
2008-08-01 17:10 ` Subdir ChangeLogs Tom Tromey
2008-08-01 17:27 ` Stan Shebs
2008-08-01 17:54 ` Tom Tromey
2008-08-01 18:44 ` Eli Zaretskii
2008-08-01 18:55 ` Tom Tromey
2008-08-01 19:25 ` Eli Zaretskii
2008-08-01 19:33 ` Tom Tromey
2008-08-01 20:11 ` Thiago Jung Bauermann
2008-08-02 7:13 ` Eli Zaretskii
2008-08-02 16:52 ` Tom Tromey
2008-08-02 17:28 ` Eli Zaretskii
2008-08-02 20:24 ` Thiago Jung Bauermann
2008-08-03 0:02 ` Michael Snyder
2008-08-01 17:40 ` RFA: Remove gdb-events Mark Kettenis
2008-07-14 17:10 ` Joel Brobecker
2008-07-14 20:33 ` Tom Tromey
2008-07-15 6:54 ` Joel Brobecker
2008-07-17 23:41 ` Tom Tromey
2008-07-21 16:54 ` GDB/MI PING (was: "Re: RFA: Remove gdb-events") Joel Brobecker
2008-07-22 0:56 ` RFA: Remove gdb-events Tom Tromey
2008-07-25 16:11 ` Tom Tromey
2008-07-20 11:46 ` Eli Zaretskii
2008-07-21 17:13 ` Vladimir Prus [this message]
2008-07-22 0:32 ` Tom Tromey
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='g62g35$l1h$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--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