From: Bob Rossi <bob@brasko.net>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Hooks still needed for annotations
Date: Wed, 01 Jun 2005 11:30:00 -0000 [thread overview]
Message-ID: <20050601113004.GC15414@white> (raw)
In-Reply-To: <17053.24737.153388.915345@farnswood.snap.net.nz>
On Wed, Jun 01, 2005 at 07:15:45PM +1200, Nick Roberts wrote:
>
> On 2004-04-21 the lines below were added to clear_interpreter_hooks in
> interps.c:
>
> deprecated_delete_breakpoint_hook = 0;
> deprecated_modify_breakpoint_hook = 0;
>
> Previously they were set to breakpoint_changed (a more natural name would be
> annotate_breakpoints_invalid). This means that sometimes breakpoints-invalid
> annotations aren't generated. In particular this is the case when a breakpoint
> is toggled between its enabled state and disabled state.
>
> Although the intention is to eventually remove annotations I don't think this
> stage has been reached yet and it makes little sense to remove a small
> number of calls. The patch below re-instates them.
Nick, in order for you to guarentee that your Emacs is working properly,
you are going to have to update the breakpoints after every command the
user types. Even though I think adding the patch is a good idea, if you
don't update the breakpoints after every command, bugs like this will
make it so that some users do not get the updated breakpoints.
For instance, make a small main program, add a breakpoint, and then
immediatly delete it. I doubt you will get the breakpoints-invalid
annotation. The problem is, even if you fix them, you still have to
check the breakpoints after every command unless you query GDB for it's
version number to see if the bug is fixed.
Bob Rossi
next prev parent reply other threads:[~2005-06-01 11:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 7:15 Nick Roberts
2005-06-01 11:30 ` Bob Rossi [this message]
2005-06-01 21:31 ` Nick Roberts
2005-06-03 19:09 ` Daniel Jacobowitz
2005-06-03 22:35 ` Nick Roberts
2005-06-03 23:59 ` Daniel Jacobowitz
2005-06-04 3:19 ` Nick Roberts
2005-07-03 17:03 ` Daniel Jacobowitz
2005-07-03 22:13 ` Nick Roberts
2005-07-03 22:44 ` Daniel Jacobowitz
2005-06-04 13:02 ` Bob Rossi
2005-06-13 3:14 ` Daniel Jacobowitz
2005-06-15 15:52 ` Bob Rossi
2005-06-15 16:07 ` Daniel Jacobowitz
2005-06-15 16:31 ` Bob Rossi
2005-07-03 16:45 ` Daniel Jacobowitz
2005-06-15 23:07 ` Nick Roberts
2005-06-15 23:29 ` Bob Rossi
2005-07-01 0:21 ` Bob Rossi
2005-07-01 1:18 ` Nick Roberts
2005-06-06 21:57 ` Nick Roberts
2005-06-10 2:26 ` Bob Rossi
2005-06-10 3:25 ` Nick Roberts
2005-06-15 15:24 ` Bob Rossi
2005-06-15 21:38 ` Nick Roberts
2005-06-15 22:58 ` Bob Rossi
2005-07-03 16:39 ` Daniel Jacobowitz
2005-07-06 15:03 ` Bob Rossi
2005-07-15 0:03 ` Daniel Jacobowitz
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=20050601113004.GC15414@white \
--to=bob@brasko.net \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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