This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB 6
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