Re: [MI/RFC] Emit ^running via observer.

[Nick Roberts <nickrob@snap.net.nz>]

 > > mi-async.exp is a test for async mode, so is not expected to pass in sync
 > > mode.
 > 
 > That's the question -- what about this test is specific to async mode?

Async mode decouples the output from the input.  This allows a CLI command that
executes the inferior to (indirectly) generate MI output.  That's why I was
interested in async mode and that's what this test is for.  The work has
actually been done for more general reasons, such as non-stop mode.  I think
the MI output is just a fortunate side-effect.

 >...
 > > It's not a problem if async mode becomes the default, which is my
 > > understanding.  
 > 
 > Not mine, unfortunately. We can't even make all target always have at least
 > one element in thread list -- which is much simpler change.

Maybe that's a requirement of non-stop mode but I'm not sure that this is
relevant here, i.e. with just async mode.

-- 
Nick                                           http://www.inet.net.nz/~nickrob