Re: Fix MI/async testsuite

[Daniel Jacobowitz <drow@false.org>]

On Sun, May 04, 2008 at 08:48:20PM +0400, Vladimir Prus wrote:
> 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".

Why should we print ^running before we are ready for more input?

*running, yes, soon as the target starts running.  But ^running is the
result of the command and should show up when the command is done,
shouldn't it?

In other words, the current version:

`OUTPUT ==>'
     `( OUT-OF-BAND-RECORD )* [ RESULT-RECORD ] "(gdb)" NL'

`RESULT-RECORD ==>'
     ` [ TOKEN ] "^" RESULT-CLASS ( "," RESULT )* NL'

Changed to this:

`OUTPUT ==>'
     `OUT-OF-BAND-RECORD | RESULT-RECORD'

`RESULT-RECORD ==>'
     ` [ TOKEN ] "^" RESULT-CLASS ( "," RESULT )* NL "(gdb)" NL'

-- 
Daniel Jacobowitz
CodeSourcery