Re: Fix MI/async testsuite

[Daniel Jacobowitz <drow@false.org>]

On Sun, May 04, 2008 at 04:18:14PM +0400, Vladimir Prus wrote:
> 
> My previous patches to add =thread-created have broken MI testsuite
> in async mode, since in async mode, the order of output is somewhat
> different and the output for -exec-run is:
> 
>   ^running
>   =thread-created
>   (gdb)
> 
> with =thread-creating going before prompt, while in sync mode 
> (gdb) follows ^running immediately.

Is this syntax only recently allowed and not yet documented?  I built
the current info docs from CVS and the grammar does not allow for
RESULT-RECORD OUT-OF-BAND-RECORD (gdb) NL.

=thread-created after *running makes lots of sense.  =thread-created
after ^running is a little weird to me.  If ^running is the response
to a command it ought to be followed by a prompt.

-- 
Daniel Jacobowitz
CodeSourcery