From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: Fix multi-fork.exp for good
Date: Sun, 30 Dec 2007 04:34:00 -0000 [thread overview]
Message-ID: <20071230043201.GA24220@caradoc.them.org> (raw)
In-Reply-To: <m3bq89vepx.fsf@codesourcery.com>
On Sat, Dec 29, 2007 at 04:59:38AM -0800, Jim Blandy wrote:
> Or at least, I hope so. I was getting occasional timeouts from
> interactions after the follow-parent tests on loaded machines. Set a
> few windows doing 'while true; do :; done' and give it a try.
Thanks. I saw this behavior too; your patch looks good to me.
> + # We don't know what order the interesting things will arrive in.
> + # Using a pattern of the form 'x|y|z' instead of -re x ... -re y
> + # ... -re z ensures that expect always chooses the match that
> + # occurs leftmost in the input, and not the pattern appearing
> + # first in the script that occurs anywhere in the input, so that
> + # we don't skip anything.
Cute trick!
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-12-30 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 14:02 Jim Blandy
2007-12-30 4:34 ` Daniel Jacobowitz [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=20071230043201.GA24220@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@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