From: Stan Shebs <stan@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Make watchthreads.exp more robust
Date: Mon, 27 Apr 2009 12:52:00 -0000 [thread overview]
Message-ID: <49F5AA4C.4060702@codesourcery.com> (raw)
In-Reply-To: <20090426193156.9F5B384890@localhost>
Doug Evans wrote:
> Hi.
>
> watchthreads.exp can errantly fail if the o/s schedules, for example,
> the thread for args[0] enough times before the thread for args[1] gets
> a chance to run.
>
> Ok to check in?
>
Yes please, this one has annoyed me too!
Stan
prev parent reply other threads:[~2009-04-27 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 19:32 Doug Evans
2009-04-27 12:52 ` Stan Shebs [this message]
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=49F5AA4C.4060702@codesourcery.com \
--to=stan@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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