Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Patch: annotations -vs- deprecated hooks
Date: Mon, 14 Jul 2008 17:27:00 -0000	[thread overview]
Message-ID: <20080714172649.GD3998@adacore.com> (raw)
In-Reply-To: <m363r9bg3q.fsf@fleche.redhat.com>

Nick: Would you like to do some testing before this patch gets checked in?
(note that this is dependent on Tom's previous "observers" patch).

Hi Tom,

> There are still a couple of hooks called by the annotations code that
> are used by gdbtk.  This setup seems weird to me.  I guess these ought
> to be replaced by observers.

I agree - I didn't check why gdbtk is dependent on annotation hooks,
but we should also ask them about it, and try to remove these hooks.

> b/gdb/ChangeLog:
> 2008-07-13  Tom Tromey  <tromey@redhat.com>
> 
> 	* annotate.h (deprecated_annotate_starting_hook): Remove.
> 	(deprecated_annotate_stopped_hook): Remove.
> 	(deprecated_annotate_exited_hook): Remove.
> 	* Makefile.in (annotate.o): Depend on observer_h.
> 	* top.c (deprecated_delete_breakpoint_hook): Remove.
> 	(deprecated_create_breakpoint_hook): Likewise.
> 	(deprecated_modify_breakpoint_hook): Likewise.
> 	* interps.c (clear_interpreter_hooks): Update for removed hooks.
> 	* breakpoint.c (mention): Don't call removed hook.
> 	(delete_breakpoint): Likewise.
> 	(disable_breakpoint): Likewise.
> 	(do_enable_breakpoint): Likewise.
> 	* annotate.c: Include observer.h.
> 	(breakpoint_changed): Change type of argument.
> 	(_initialize_annotate): Register observers.
> 	(deprecated_annotate_starting_hook): Remove.
> 	(deprecated_annotate_stopped_hook): Remove.
> 	(deprecated_annotate_exited_hook): Remove.
> 	(annotate_starting): Update for hook removal.
> 	(annotate_stopped): Likewise.
> 	(annotate_exited): Likewise.
> 	* defs.h (deprecated_delete_breakpoint_hook): Remove.
> 	(deprecated_create_breakpoint_hook): Likewise.
> 	(deprecated_modify_breakpoint_hook): Likewise.

This looks good to me. We have to wait a little bit for Vladimir's
comments before you can commit the observers patch, so that should give
Nick a little bit of time to do any testing he might need (although
ideally running the testsuite should be enough).

-- 
Joel


  parent reply	other threads:[~2008-07-14 17:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13 21:59 Tom Tromey
2008-07-13 22:26 ` Nick Roberts
2008-07-13 23:15   ` Tom Tromey
2008-07-14  0:20     ` Nick Roberts
2008-07-14  0:50       ` Tom Tromey
2008-07-14  0:57         ` Daniel Jacobowitz
2008-07-14  1:37         ` Nick Roberts
2008-07-14 15:22           ` Tom Tromey
2008-07-14  5:00 ` Joel Brobecker
2008-07-14 17:27 ` Joel Brobecker [this message]
2008-07-14 17:46   ` Tom Tromey
2008-07-16 12:42   ` Nick Roberts
2008-07-28 17:50   ` 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=20080714172649.GD3998@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@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