This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Fix recent gdb.mi testsuite "unknown output after running"
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Date: Thu, 21 May 2009 03:16:29 +0100
- Subject: Re: [patch] Fix recent gdb.mi testsuite "unknown output after running"
- References: <20090520183209.GA12914@host0.dyn.jankratochvil.net>
On Wednesday 20 May 2009 19:32:10, Jan Kratochvil wrote:
> recently getting on Fedora 11 (=Rawhide) x86_64:
>
> FAIL: gdb.mi/mi-nsintrall.exp: mi runto main (unknown output after running)
> ERROR: mi-nsintrall.exp tests suppressed
> FAIL: gdb.mi/mi-async.exp: start: stop (unknown output after running)
> FAIL: gdb.mi/mi-async.exp: restart: stop (unknown output after running)
> FAIL: gdb.mi/mi-nsmoribund.exp: mi runto main (unknown output after running)
> ERROR: mi-nsmoribund.exp tests suppressed
> FAIL: gdb.mi/mi-nonstop.exp: mi runto main (unknown output after running)
> ERROR: mi-nonstop.exp tests suppressed
> FAIL: gdb.mi/mi-nonstop-exit.exp: mi runto main (unknown output after running)
> ERROR: mi-nonstop-exit.exp tests suppressed
>
> but it is more a bug in the testsuite as GDB output looks valid (below).
>
> Attaching a quick fix, just I understand an MI grammar compliant parser would
> be better for the testsuite.
I'd like to understand what caused this. This is probably related
to my recent changes to linux-nat.c to rework async mode, and add
multiprocess, although I wasn't seeing this when I commited them.
--
Pedro Alves