Re: MI testsuite fix

Luis Machado
2008-04-10T20:37:14Z

Thanks for the patch.

On Thu, 2008-04-10 at 21:02 +0100, Pedro Alves wrote:
> Fixing this leaves me with one MI regression, mi-pending.exp, which is
> related to throwing an exception running the exec cleanups, which deletes
> the MI token, when it shouldn't. That is fixed by Vladimir's pending
> "murder exec cleanup" patch, or when the token in *stopped is removed.
> Both will go in very soon.

This is still happening on PPC. So i assume this will be fixed with
Vladimir's patch as well.

There is an additional failure in the MI testsuite (PPC) when running in
asynch mode, mi-simplerun.exp and mi2-simplerun.exp, which seems to be
an output ordering issue as well.

"Correct" output:
220-exec-continue^M
220^running^M
(gdb) ^M
Hello, World!callme^M
callme^M
220*stopped,reason="exited-normally"^M
(gdb) ^M
PASS: gdb.mi/mi-simplerun.exp: continue to end

"Incorrect" output:
220-exec-continue^M
220^running^M
Hello, World!callme^M
callme^M
(gdb) ^M
FAIL: gdb.mi/mi-simplerun.exp: continue to end (failed to resume)

Correct and incorrect between "" because both ending results are valid.

This is not fixed by your latest patch, Pedro. What do you think?

Regards,

--
Luis Machado
Software Engineer
IBM Linux Technology Center