Re: [rfc] Annotation level THREE

[Nick Roberts <nick@nick.uklinux.net>]

 > > I don't really follow this. It looks like level three annotations will have
 > > a lot of the annotations missing.
 > 
 > Yes.
 > 
 > The change should remove the annotations that were being used to mark up 
 > CLI output, but leave those that were notifying the GUI of various events.
 > 
 > The marked up output has been superseeded by ``interpreter mi ...''.
 > 
 >  > To currently work gdb-ui.el needs:
 > > 
 > > 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
 > > display-begin
 > > display-end
 > > display-number-end
 > > array-section-begin
 > > array-section-end
 > > field-begin
 > > field-end
 > > 
 > > It needn't use frames-invalid and breakpoints-invalid which are repeatedly
 > > generated during a run and possibly other selected ones could go. However,
 > > some appear to be essential e.g display-begin as the MI equivalent,
 > > -display-insert, isn't implemented and I don't know how to make use of
 > > variable objects.
 > 
 > Why do you need display-{begin,end}?  -display-insert has been made 
 > redundant by the varobj stuff - it lets the GUI efficiently track its 
 > display values outside of the CLI.  

Variable objects don't auto-display. You seem to have to type
-var-evaluate-expression each time the program stops. 

 >  The testsuite is a good source of 
 > varobj examples (unfortunatly lacking from the doco):
 > http://sources.redhat.com/gdb/current/onlinedocs/gdb_25.html#SEC565

The lack of documentation for (and apparent completeness of) GDB/MI is part of
the problem. I realise that I have no service agreement and cannot expect
anything but I would prefer more effort to be directed towards MI before (a
large number of) annotations are removed.

 > The above list also contains thing like field-{begin,end}, 
 > array-section-{begin,end} et.al.  Why are they needed.

I use them to parse the output. They could probably go, if necessary, but
others that you plan to take out *are* needed.

Nick