Re: asynchronous MI output commands

[Daniel Jacobowitz <drow@false.org>]

On Fri, May 05, 2006 at 09:27:06PM -0400, Bob Rossi wrote:
> The first problem that I've run into is determining if an MI output
> command is synchronous or asynchronous. I can tell if the MI output
> command is asynchronous by looking for, reason="abc", like below,
>   47*stopped,reason="end-stepping-range",thread-id="0", ...

`ASYNC-RECORD ==>'
     `EXEC-ASYNC-OUTPUT | STATUS-ASYNC-OUTPUT | NOTIFY-ASYNC-OUTPUT'

`EXEC-ASYNC-OUTPUT ==>'
     `[ TOKEN ] "*" ASYNC-OUTPUT'

`STATUS-ASYNC-OUTPUT ==>'
     `[ TOKEN ] "+" ASYNC-OUTPUT'

`NOTIFY-ASYNC-OUTPUT ==>'
     `[ TOKEN ] "=" ASYNC-OUTPUT'

Why can't you tell that output is asynchronous from the *stopped, as
opposed to ^done?

-- 
Daniel Jacobowitz
CodeSourcery