From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [patch] Fix recent gdb.mi testsuite "unknown output after running"
Date: Thu, 21 May 2009 02:16:00 -0000 [thread overview]
Message-ID: <200905210316.30122.pedro@codesourcery.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2009-05-21 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 18:32 Jan Kratochvil
2009-05-21 2:16 ` Pedro Alves [this message]
2009-05-21 13:46 ` Pedro Alves
2009-05-21 15:54 ` [commit] New target_wait `options' argument, and new TARGET_WNOHANG option. (was: Re: [patch] Fix recent gdb.mi testsuite "unknown output after running") Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905210316.30122.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox