Re: Fix MI/async testsuite

[Vladimir Prus <vladimir@codesourcery.com>]

On Sunday 04 May 2008 20:33:21 Daniel Jacobowitz wrote:
> 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.

Guess this is because I did not update the grammar per earliner discussion.
We should have RESULT-RECORD, OUT-OF-BAND-RECORD and PROMPT be independent,
and allowed to appear in any order.

> =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.

Per current grammar, yes. In principle, no -- prompt indicates that gdb
is ready to accept further input, and should be printed, naturally, when
gdb is ready to accept more input -- which is not necessary right after
printing "^running".

- Volodya