From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: msnyder@redhat.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com, jjohnstn@redhat.com
Subject: Re: [rfa/testsuite/threads] manythreads.exp: cancel outstanding after-blocks
Date: Fri, 07 May 2004 12:46:00 -0000 [thread overview]
Message-ID: <20040507124625.6DB474B104@berman.michael-chastain.com> (raw)
Daniel Jacobowitz writes:
> That's a nice trick, I didn't know it. But it's simpler to just make
> the stop synchronous... would you mind trying that instead?
Sure, I can do it that synchronously. This fixes the problems with
print-threads.exp the same way. I get more frequent gdb internal
errors when running this test with a synchronous sleep, but that's
good for a test script.
Tested again on native i686-pc-linux-gnu, red hat 8.0, group of 12
test runs before and after.
OK to commit?
Michael C
2004-05-07 Michael Chastain <mec.gnu@mindspring.com>
Fix PR gdb/1636.
* gdb.threads/manythreads.exp: Change asynchronous 'after'
calls to synchronous.
Index: gdb.threads/manythreads.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/manythreads.exp,v
retrieving revision 1.1
diff -c -3 -p -r1.1 manythreads.exp
*** gdb.threads/manythreads.exp 22 Apr 2004 22:19:40 -0000 1.1
--- gdb.threads/manythreads.exp 7 May 2004 12:41:39 -0000
*************** gdb_test_multiple "continue" "first cont
*** 60,66 ****
}
# Send a Ctrl-C and verify that we can do info threads and continue
! after 1000 {send_gdb "\003"}
set message "stop threads 1"
gdb_test_multiple "" "stop threads 1" {
-re "\\\[New \[^\]\]*\\\]\r\n" {
--- 60,67 ----
}
# Send a Ctrl-C and verify that we can do info threads and continue
! after 1000
! send_gdb "\003"
set message "stop threads 1"
gdb_test_multiple "" "stop threads 1" {
-re "\\\[New \[^\]\]*\\\]\r\n" {
*************** gdb_test_multiple "continue" "second con
*** 93,99 ****
}
# Send another Ctrl-C and verify that we can do info threads and quit
! after 1000 {send_gdb "\003"}
set message "stop threads 2"
gdb_test_multiple "" "stop threads 2" {
-re "\\\[New \[^\]\]*\\\]\r\n" {
--- 94,101 ----
}
# Send another Ctrl-C and verify that we can do info threads and quit
! after 1000
! send_gdb "\003"
set message "stop threads 2"
gdb_test_multiple "" "stop threads 2" {
-re "\\\[New \[^\]\]*\\\]\r\n" {
next reply other threads:[~2004-05-07 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 12:46 Michael Elizabeth Chastain [this message]
2004-05-12 0:10 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-05-07 6:09 Michael Elizabeth Chastain
2004-05-07 6:14 ` Daniel Jacobowitz
2004-05-07 6:08 Michael Elizabeth Chastain
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=20040507124625.6DB474B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.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