This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Testsuite failures in gdb.gdb/selftest.exp
- From: Andreas Schwab <schwab at suse dot de>
- To: gdb-patches at sourceware dot org
- Date: Wed, 31 Jan 2007 18:12:37 +0100
- Subject: Testsuite failures in gdb.gdb/selftest.exp
With heavy optimizations there can be even more code reordering, causing
spurious failures in do_steps_and_nexts.
The quit_flag case was seen on ppc, the gdb_std{out,err} cases on ia64.
Andreas.
2007-01-31 Andreas Schwab <schwab@suse.de>
* gdb.gdb/selftest.exp (do_steps_and_nexts): Add more matches.
--- gdb/testsuite/gdb.gdb/selftest.exp.~1.10.~ 2007-01-10 11:18:59.000000000 +0100
+++ gdb/testsuite/gdb.gdb/selftest.exp 2007-01-31 18:02:16.000000000 +0100
@@ -177,6 +177,10 @@ proc do_steps_and_nexts {} {
set description "step over ndir initialization"
set command "step"
}
+ -re ".*quit_flag = 0.*$gdb_prompt $" {
+ set description "step over quit_flag initialization"
+ set command "step"
+ }
-re ".*instream = stdin.*$gdb_prompt $" {
set description "step over instream initialization"
set command "step"
@@ -185,6 +189,14 @@ proc do_steps_and_nexts {} {
set description "next over getcwd"
set command "next"
}
+ -re ".*gdb_stdout = stdio_fileopen .stdout.;.*$gdb_prompt $" {
+ set description "step over gdb_stdout initialization"
+ set command "step"
+ }
+ -re ".*gdb_stderr = stdio_fileopen .stderr.;.*$gdb_prompt $" {
+ set description "step over gdb_stderr initialization"
+ set command "step"
+ }
-re "\[ \t\]+\{\r\n$gdb_prompt $" {
setup_xfail "mips-*-irix5*"
fail "$description ended up at odd location"
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."