From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>, Marek Polacek <mpolacek@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] [patch] testsuite: MI: racy results in async mode #2
Date: Tue, 01 Nov 2011 20:01:00 -0000 [thread overview]
Message-ID: <20111101200114.GA15541@host1.jankratochvil.net> (raw)
In-Reply-To: <4EB01DA9.9080207@redhat.com> <m31utr4xyd.fsf@fleche.redhat.com>
On Tue, 01 Nov 2011 17:19:38 +0100, Tom Tromey wrote:
> I think if it works then it is clearly better than what we have now.
OK, checked in so that I can further watch the racy behavior:
http://sourceware.org/ml/gdb-cvs/2011-11/msg00005.html
> One other idea would be to send an "output" command so that you could
> match some known output to sync up correctly. I'm not sure if this
> would always work though.
From some level of difficulty on I would rather prefer the MI parser.
On Tue, 01 Nov 2011 17:26:17 +0100, Marek Polacek wrote:
> This fixes those 5 FAILs I've seen. Tested with writew.so on x86_64-unknown-
> linux-gnu.
Great, thanks.
Regards,
Jan
next prev parent reply other threads:[~2011-11-01 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 10:16 [patch] testsuite: MI: racy results in async mode (PR testsuite/12649) Jan Kratochvil
2011-10-27 16:49 ` Tom Tromey
2011-10-28 8:51 ` [commit] " Jan Kratochvil
2011-10-29 10:36 ` [patch] testsuite: MI: racy results in async mode #2 Jan Kratochvil
2011-10-29 12:10 ` Marek Polacek
2011-10-29 12:15 ` Marek Polacek
2011-10-29 15:09 ` Jan Kratochvil
2011-10-29 16:01 ` Marek Polacek
2011-11-01 16:20 ` Tom Tromey
2011-11-01 20:01 ` Jan Kratochvil [this message]
2011-11-01 16:26 ` Marek Polacek
2011-11-01 15:40 ` [patch] testsuite: MI: racy results in async mode (PR testsuite/12649) Doug Evans
2011-11-01 16:26 ` Jan Kratochvil
2011-11-01 18:55 ` Tom Tromey
2011-11-01 22:46 ` Doug Evans
2011-11-02 17:31 ` Tom Tromey
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=20111101200114.GA15541@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mpolacek@redhat.com \
--cc=tromey@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