public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: GDB 6
Date: Mon, 12 May 2003 19:36:00 -0000	[thread overview]
Message-ID: <20030512193653.GB18114@white> (raw)
In-Reply-To: <20030511201320.0C21675FDD@nick.uklinux.net>

On Sun, May 11, 2003 at 09:13:20PM +0100, Nick Roberts wrote:
> 
>  > > Here is a revised and reduced list of annotations that I think I could
>  > > work with:
>  > > 
>  > > frames-invalid
>  > > breakpoints-invalid
>  > > pre-prompt
>  > > prompt
>  > > commands
>  > > overload-choice
>  > > query
>  > > prompt-for-continue
>  > > post-prompt
>  > > source
>  > > starting
>  > > exited
>  > > signalled
>  > > signal
>  > > breakpoint
>  > > watchpoint
>  > > frame-begin
>  > > stopped
>  > 
>  > I'm not sure about frame begin.  Things like frames-invalid are events 
>  > and they can stay (forever? ...).
>  > 
> 
> I don't really need frame-begin. The problem that I have, however, is that
> frame-begin (and other annotations) are issued *before* stopped. This meant
> that sometimes Emacs thought that frame details output by Gdb were output by
> the inferior and so they were displayed in the IO buffer. I can only reproduce
> this problem now with tbreak where a typical annotation sequence (avoiding
> many repeats) looks like:
> 
> frames-invalid
> breakpoints-invalid
> starting                <--
> frames-invalid
> breakpoints-invalid
> frame-begin etc         <--
> source
> frame-end
> stopped                 <--
> 

Also, do you relize that breakpoint-invalid is buggy?
For many versions, gdb will not output breakpoints-invalid when you
delete the last breakpoint in the list.

so, 

b main
delete main

you will not get a breakpoints-invalid and emacs will still be
displaying a breakpoint.

Bob Rossi

  parent reply	other threads:[~2003-05-12 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 22:35 Nick Roberts
2003-05-11 15:22 ` Andrew Cagney
2003-05-12 18:57   ` Nick Roberts
2003-05-11 22:00     ` Andrew Cagney
2003-05-12 19:29     ` Bob Rossi
2003-05-13 17:47       ` Nick Roberts
2003-05-12 19:36     ` Bob Rossi [this message]
2003-05-13 17:47       ` Nick Roberts
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 18:17 Michael Elizabeth Chastain
2003-05-09 20:25 ` Andrew Cagney
2003-05-09 16:58 Andrew Cagney
2003-05-09 17:12 ` Daniel Jacobowitz
2003-05-09 17:41   ` Elena Zannoni
2003-05-09 18:05 ` Bob Rossi
2003-05-09 20:21   ` 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=20030512193653.GB18114@white \
    --to=bob_rossi@cox.net \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).