From: Jeff Johnston <jjohnstn@redhat.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite/threads] ping: manythreads.exp
Date: Thu, 03 Jun 2004 19:31:00 -0000 [thread overview]
Message-ID: <40BF7C7A.60701@redhat.com> (raw)
In-Reply-To: <20040603182804.D59554B104@berman.michael-chastain.com>
Michael Elizabeth Chastain wrote:
> ms> So... this means it will unconditionally wait, right?
> ms> Can I assume that "after 1000" means milliseconds, not seconds?
>
> Yes, and yes. The "milliseconds" part is in the TCL book so it's
> okay to rely on it.
>
> ms> That's my only concern, that if it fails for some reason, it
> ms> will block for a long time. If that's not the case, then the
> ms> change is ok with me (if it's ok with Jeff).
>
> Hey Jeff -- is this okay with you?
>
Yes, please go ahead.
> ms> Michael, I notice that the same idiom is used in pthreads.exp;
> ms> do you think your change would also be appropriate there, and
> ms> if so, would you mind making it?
>
> I think it would be good there too. Right now, the code says:
>
> sleep 1
> set description "Stopped with a ^C"
> after 1000 [send_gdb "\003"]
> gdb_expect {
> ...
> }
>
> so the test script is going into the gdb_expect and pausing there
> until the 'after' block executes. There's no need to be running
> the send_gdb "\003" in parallel with gdb_expect. So I'll make a
> patch for this too. (Also it looks bizarre to use both 'sleep'
> and 'after' ... gotta do a little research).
>
> Michael C
>
next prev parent reply other threads:[~2004-06-03 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 18:28 Michael Elizabeth Chastain
2004-06-03 19:31 ` Jeff Johnston [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 17:34 Michael Elizabeth Chastain
2004-06-03 18:07 ` Michael Snyder
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=40BF7C7A.60701@redhat.com \
--to=jjohnstn@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=msnyder@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