Re: Fix MI/async testsuite

[Vladimir Prus <vladimir@codesourcery.com>]

On Sunday 04 May 2008 21:22:34 Daniel Jacobowitz wrote:
> On Sun, May 04, 2008 at 01:14:30PM -0400, Daniel Jacobowitz wrote:
> > 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?
> 
> Duh, this is because of sync mode, right?  Anyway, it seems like "gdb
> accepts input after -exec-continue" and "gdb uses *running instead of
> ^running" should have the same condition, to avoid this weird output.

Well, ideally, ^running should not exist. When gdb is done with a command,
it should always print ^done, and since it's done with a command, print a
prompt. Unfortunately, right now ^running exists and does something fairly
strange:

- in sync mode, you get "^running" + "(gdb)" before even trying to resume
target
- in async mode you get "^running" + random output + "(gdb)"
- in async mode when running CLI command, you get "^running" + "^done"

This is a mess, but I don't think we should/can fix this mess without
going to MI3.

- Volodya