Re: RFC: MI output during program execution

[Daniel Jacobowitz <drow at false dot org>]

On Tue, Aug 09, 2005 at 08:48:26PM -0400, Bob Rossi wrote:
> Here is another odd scenario, Jim, please give some info if you have
> experience in this area.
> 
> If you hit a breakpoint, and the observer starts to send you data, does
> it 
>    - send all the state data in one async response, in the same response as
>      the async MI command that says *stopped?
>    - send all the state data in one async response, in a different response 
>      as the async MI command that says *stopped?
>    - send all the state data, each in different async response's, in a 
>      different response as the async MI command that says *stopped?
> 
> This may seem unimportant, however I believe it could be marginally
> important. For instance, does the front end have to wait for the async
> observer response before it can do anything else?

I can't speak for what Apple's done, but it seems natural to me like
#3.  "state data" isn't a great term for this; they're notifications of
things, as they happen.  So it seems to me that you'd want something
like (forgive my syntax, don't take this literally!  I don't speak MI
at the moment):

=breakpoint-changed,[bpnum="1",state="disabled"]
=thread-changed,[thread="2"]

-- 
Daniel Jacobowitz
CodeSourcery, LLC