Re: GDB 6

[Nick Roberts <nick at nick dot uklinux dot net>]

 > > 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                 <--

Using break instead of tbreak, the breakpoint annotation is issued before
frame-begin which tells Emacs that output is now from Gdb and not the
inferior.

Before frame-begin is deleted, can Gdb issue another annotation (stopping ?)
prior to printing frame details so that Emacs will always understand that this
is output from Gdb?

Also Emacs doesn't need prompt-for-continue.

Nick