--- Begin Message ---
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: msnyder at redhat dot com
- Cc: drow at mvista dot com, gdb-patches at sources dot redhat dot com,jjohnstn at redhat dot com
- Date: Fri, 7 May 2004 08:46:25 -0400 (EDT)
- Subject: Re: [rfa/testsuite/threads] manythreads.exp: cancel outstanding after-blocks
- Delivery-date: Fri, 07 May 2004 09:33:46 -0400
- Envelope-to: cagney@gnu.org
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" {
--- End Message ---