From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Robustify mi-simplerun.
Date: Fri, 13 Jun 2008 20:13:00 -0000 [thread overview]
Message-ID: <20080613200035.GA31920@caradoc.them.org> (raw)
In-Reply-To: <200806132355.42833.vladimir@codesourcery.com>
On Fri, Jun 13, 2008 at 11:55:42PM +0400, Vladimir Prus wrote:
> The program been run by this testcase produces output. Since GDB prints
> the *running notification, and the prompt, after actually resuming the program,
> there's a race condition -- the program may produce the output before gdb prints
> the prompt, which breaks the test. This patch add artificial delay to the
> program to make sure gdb print the prompt first.
Is the output necessary for any test? If not, can we just remove it?
Sleep is bad. Someone'll run the testsuite on a machine with load
(e.g. our nightly tester) and it'll fail again.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-06-13 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 20:10 Vladimir Prus
2008-06-13 20:13 ` Daniel Jacobowitz [this message]
2008-06-13 21:08 ` Vladimir Prus
2008-06-13 21:13 ` Daniel Jacobowitz
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=20080613200035.GA31920@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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