This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[ob] More test timeouts
- From: Daniel Jacobowitz <dan at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Mon, 1 Feb 2010 12:52:13 -0500
- Subject: [ob] More test timeouts
Two more timeouts I encountered: one failure to reset an extended
timeout, which did not turn up in my earlier batch because it is
native only, and one timeout of interrupt.exp which fails with
x86_64 -m32. Checked in as obvious.
--
Daniel Jacobowitz
CodeSourcery
2010-02-01 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.base/bigcore.exp: Reset increased timeout.
* gdb.base/interrupt.exp: Match unexpected gdb prompt.
Index: gdb.base/bigcore.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/bigcore.exp,v
retrieving revision 1.20
diff -u -p -r1.20 bigcore.exp
--- gdb.base/bigcore.exp 1 Jan 2010 07:32:00 -0000 1.20
+++ gdb.base/bigcore.exp 1 Feb 2010 17:43:23 -0000
@@ -147,6 +147,7 @@ gdb_test_multiple "info program" $test {
set oldtimeout $timeout
set timeout 600
gdb_test "signal SIGABRT" "Program terminated with signal SIGABRT, .*"
+set timeout $oldtimeout
# Find the corefile
set file ""
Index: gdb.base/interrupt.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/interrupt.exp,v
retrieving revision 1.15
diff -u -p -r1.15 interrupt.exp
--- gdb.base/interrupt.exp 1 Jan 2010 07:32:01 -0000 1.15
+++ gdb.base/interrupt.exp 1 Feb 2010 17:43:23 -0000
@@ -167,6 +167,7 @@ if ![file exists $binfile] then {
# here.
gdb_expect {
-re "^(\r\n|)data\r\n(|data\r\n)$" { pass "echo data" }
+ -re "Undefined command.*$gdb_prompt " { fail "echo data" }
timeout { fail "echo data (timeout)" }
eof { fail "echo data (eof)" }
}