[mi] organize possible exec async mi oc command reasons

[Bob Rossi]

On Thu, Mar 24, 2005 at 09:57:35PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 24 Mar 2005 10:46:02 -0500
> > From: Bob Rossi <bob@brasko.net>
> > 
> > Eli, if you can think of a better way for me to add to the doco, let me
> > know.
> 
> I'm sorry to say that I don't understand the text you wrote.  My
> problem starts right with the first sentence:
> 
>     +The following lists the current set of reasons why @sc{gdb/mi} would
>     +return with *stopped (exec-async-output).  
> What does this sentence mean? and why there's a `*' before "stopped"?
> and what's with the "exec-async-output" inside parens?
> 

How about I replace that with this, 

The following enumerates the current set of reasons why @sc{gdb/mi} would
return with an @var{exec-async-output} command.

> Also, I couldn't parse sentences like this in the itemized list:
> 
>     +A breakpoint was reached, "breakpoint-hit"
> 
> This is not an English sentence, AFAIU.

The list is suppossed to be all of the reasons why GDB would return an
exec async output command to the FE.

The first part of each item is a description of why GDB returned, the
second part is the actual reason GDB/MI will give. 
(ie "reason=breakpoint-hit").

Thanks,
Bob Rossi