Re: RFA (?) Annotate Level 3 patch

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

 > > Moving annotate_stopped to the start of normal_stop seems to do the right
 > > thing. It might be bad practice, however, to break existing functionality
 > > so a better solution might be to create a new annotation there - aargh! -
 > > called stopping, say, instead. However, remember that I will have reduced
 > > my initial set of 25 annotations to 14. They would be:
 > > 
 > > 
 > >     pre-prompt            prompt            post-prompt
 > >     commands              overload-choice   query
 > >     prompt-for-continue   source            starting
 > >     exited                signalled         signal
 > >     stopped
 > > 
 > >     and stopping
 > 
 > Could stopped be zapped from annotate level-3 then?

Well "stopped" is in my list above as a conservative measure to keep existing
functionality. Since all stop (normal or otherwise) seem to go through
normal_stop, I think that one annotation (called stopped or stopping) at the
start of this procedure is sufficient for my purposes.

On a related matter, as the Machine Interface evolves, Emacs will have to do
different things for different versions of GDB, so it would be helpful if
"show version" ("-gdb-show version") or a related command gave a formally
defined increasing version number. In Emacs, the last release is 21.3.1 and
the version in CVS is 21.3.50. In GDB, the last release is 6.0 but the version
in CVS is 2004-02-01-cvs, say. Also releases, like 5.3postxxxx.. exist.

Perhaps I can get a mode to work just with GDB/MI before the next release of
Emacs from HEAD, which is where my code resides. However, unlike GDB, Emacs has
no schedule ;-)

Nick