Re: Fix MI/async testsuite

[Daniel Jacobowitz <drow@false.org>]

On Sun, May 04, 2008 at 09:38:01PM +0400, Vladimir Prus wrote:
> 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.

For MI2, why can't we leave ^running always followed by a prompt?  We
fail to accept input at that prompt in sync mode, which is a known
bug, but that's life.

I don't think having ^result followed by =EVENT followed by (gdb)
makes sense, and it's a new broken behavior, not an old one.

-- 
Daniel Jacobowitz
CodeSourcery