Re: MI -break-info command issues

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 27 Jan 2006 12:17:17 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
> 
> > Historically, GDB/MI was added to the sources without _any_
> > documentation.  I needed to lobby those who wrote the code to make
> > some docs available, and finally got a kind of white paper that
> > described what MI _will_ look like; it goes without saying that the
> > reality was quite different.  I then needed to edit that document
> > heavily to make it fit into the manual (convert chapters to sections,
> > sections to subsections, fix style and Texinfo usage, etc.) and that
> > is what we have now, basically, except that some portions were
> > improved since then, whenever commands were added/changed.
> 
> Eli, one thought I had recently was this. I would like to automate the
> examples, using the testsuite. So that if an MI output command changed,
> the sample would be updated. Do you think this would be possible to do?

I don't like the idea of asking people to install dejagnu+expect just
to produce the docs.

Perhaps we could instead come up with some way of running each of the
MI commands through "gdb -i mi", and capturing the output to produce
the examples for the manual.  If you wish to work on this, I'd support
such a change.  It would involve extracting the MI commands from the
manual, running GDB, capturing the output, and inserting it into the
examples.