Re: MI output command error

[Bob Rossi <bob@brasko.net>]

On Thu, Mar 10, 2005 at 04:08:48PM -0500, Daniel Jacobowitz wrote:
> On Thu, Mar 10, 2005 at 03:47:38PM -0500, Bob Rossi wrote:
> > > I'm as mystified as Dave as to how you could read the manual and
> > > believe GDB/MI was designed to operate synchronously.  A number of MI
> > > commands have documentation that begins with "Asynchronous command." In
> > > particular, look at -exec-interrupt, which makes no sense as a
> > > synchronous command.
> > 
> > Hey, I'm still learning here, just make sure you don't confuse
> > mystified/stupid :)
> > 
> > I've been used to working with the a2 interace, which wasn't
> > asyncronous.
> 
> What do you mean by "a2"?

Annotate 2

> > Do you guys know if the MI always works asyncronously? Or
> > are there modes when it has to work syncronously?
> 
> _MI_ is defined to be asynchronous.  Any asynchronous interface may
> appear synchronous under some conditions.
> 
> How asynchronous it is depends on the target; most targets are not
> fully async.

Thanks for the help, it is *very* much appreciated.

Bob Rossi