OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

PR gdb/1738 

* gdb.base/signals.exp (signal_tests_1): KFAIL bug in continuing
	from a breakpoint with a pending signal.
This commit is contained in:
Daniel Jacobowitz 2004-08-09 13:17:34 +00:00
parent 04f6ecf279
commit 1a5ce3f34d
2 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
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.
2004-08-08 Daniel Jacobowitz <dan@debian.org>
PR gdb/1736

15
gdb/testsuite/gdb.base/signals.exp
View File

@ -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"