This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[testsuite] Kfail signals.exp failures
- From: Daniel Jacobowitz <drow at false dot org>
- To: gdb-patches at sources dot redhat dot com
- Cc: Michael Chastain <mec dot gnu at mindspring dot com>
- Date: Sun, 8 Aug 2004 19:18:10 -0400
- Subject: [testsuite] Kfail signals.exp failures
Andrew removed some "suspicious" xfails in signals.exp when he
overhauled it. They're a legitimate bug in GDB; I've put a complete
analysis in PR 1738. I expect all hardware single step targets to
fail; I maintained the previous list from the removed setup_xfails
(and added x86_64).
OK?
--
Daniel Jacobowitz
2004-08-08 Daniel Jacobowitz <dan@debian.org>
PR gdb/1738
* gdb.base/signals.exp (signal_tests_1): KFAIL bug in continuing
from a breakpoint with a pending signal.
Index: testsuite/gdb.base/signals.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/signals.exp,v
retrieving revision 1.8
diff -u -p -r1.8 signals.exp
--- testsuite/gdb.base/signals.exp 20 Jul 2004 19:59:26 -0000 1.8
+++ testsuite/gdb.base/signals.exp 8 Aug 2004 23:16:17 -0000
@@ -114,9 +114,24 @@ proc signal_tests_1 {} {
# In running to func2, the 2rd alarm call will have been set
# up, let it be delivered.
+ # This doesn't work correctly on platforms with hardware single
+ # step...
+
sleep 2
+
+ setup_kfail "i*86-*-*" gdb/1738
+ setup_kfail "x86_64-*-*" gdb/1738
+ setup_kfail "rs6000-*-*" gdb/1738
+ setup_kfail "powerpc-*-*" gdb/1738
+ setup_kfail "sparc-*-*" gdb/1738
gdb_test "continue" "Breakpoint.*handler.*" \
"continue to handler for 3rd alarm call"
+
+ setup_kfail "i*86-*-*" gdb/1738
+ setup_kfail "x86_64-*-*" gdb/1738
+ setup_kfail "rs6000-*-*" gdb/1738
+ setup_kfail "powerpc-*-*" gdb/1738
+ setup_kfail "sparc-*-*" gdb/1738
gdb_test "backtrace" \
"#0 handler.*#1.*signal handler called.*#2 func2.*#3.*main.*" \
"backtrace for 3rd alarm"