[ob] Remove a dejagnu ERROR from auxv.exp
Daniel Jacobowitz
drow@false.org
Thu Jun 22 19:35:00 GMT 2006
If your target does not support gcore at all, then it will currently
generate an ERROR running auxv.exp. This turns it into an UNSUPPORTED,
as was probably intended.
We have some nightly build machinery here at CodeSourcery which can
automatically run DejaGNU testsuites. It normally shows us nice pleasant
deltas between runs, but it's set to always include ERRORs, since they're
supposed to indicate a problem in the testsuite rather than in the tool
being tested.
Tested on x86_64-pc-linux-gnu and committed.
--
Daniel Jacobowitz
CodeSourcery
2006-06-22 Daniel Jacobowitz <dan@codesourcery.com>
* auxv.exp: Intercept undefined command messages before
gdb_test_multiple does.
Index: gdb-20060226/gdb/testsuite/gdb.base/auxv.exp
===================================================================
--- gdb-20060226.orig/gdb/testsuite/gdb.base/auxv.exp 2006-06-13 21:06:57.000000000 -0700
+++ gdb-20060226/gdb/testsuite/gdb.base/auxv.exp 2006-06-13 21:07:09.000000000 -0700
@@ -139,6 +139,9 @@ gdb_test_multiple "gcore $gcorefile" "gc
-re "Can't create a corefile\[\r\n\]+$gdb_prompt $" {
unsupported "gcore"
}
+ -re "Undefined command: .*\[\r\n\]+$gdb_prompt $" {
+ unsupported "gcore"
+ }
}
# Let the program continue and die.
More information about the Gdb-patches
mailing list