old-cross-binutils/gdb/testsuite/gdb.base/signals.exp
Fred Fish d9538961cc * gdb.base/a1-selftest.exp (do_steps_and_nexts): New routine to
encapsulate all the steps/nexts done during self test, starting
	at main, and makes them less sensitive to optimization issues.
	Add "hppa*-*-hpux*" to setup_xfail for "backtrace through
	signal handler" test.
	* gdb.threads/pthreads.exp: Only run this for native configs.
	* gdb.base/signals.exp (test_handle_all_print): Remove code that
	increased timeouts, it now makes no difference.
	* gdb.base/structs.exp (do_function_calls): Add hppa*-*-hpux9*"
	setup_xfails for "p fun5()", "p fun6()", "p fun7()", and "p fun8"
	tests.
	gdb.c++/virtfunc.exp (do_tests): Add "mips-*-irix5*" setup_xfail
	for "runto test_calls(void)" test.
1996-08-12 22:38:30 +00:00

617 lines
26 KiB
Text

if $nosignals {
verbose "Skipping signals.exp because of nosignals."
continue
}
if $tracelevel then {
strace $tracelevel
}
set prms_id 0
set bug_id 0
set testfile signals
set srcfile ${testfile}.c
set binfile ${objdir}/${subdir}/${testfile}
if { [compile "${srcdir}/${subdir}/${srcfile} -g -o ${binfile}"] != "" } {
perror "Couldn't compile ${srcfile}"
return -1
}
# Create and source the file that provides information about the compiler
# used to compile the test case.
execute_anywhere "rm -f ${binfile}.ci"
if { [compile "-E ${srcdir}/${subdir}/compiler.c > ${binfile}.ci"] != "" } {
perror "Couldn't make ${binfile}.ci file"
return -1
}
source ${binfile}.ci
proc signal_tests_1 {} {
global prompt
if [runto_main] then {
gdb_test "next" "signal \\(SIGUSR1.*" \
"next over signal (SIGALRM, handler)"
gdb_test "next" "alarm \\(.*" \
"next over signal (SIGUSR1, handler)"
gdb_test "next" "\\+\\+count; /\\* first \\*/" \
"next over alarm (1)"
# An alarm has been signaled, give the signal time to get delivered.
exec sleep 2
# i386 BSD currently fails the next test with a SIGTRAP.
setup_xfail "i*86-*-bsd*"
# But Dynix has a DECR_PC_AFTER_BREAK of zero, so the failure
# is shadowed by hitting the through_sigtramp_breakpoint.
clear_xfail "i*86-sequent-bsd*"
# Univel SVR4 i386 continues instead of stepping.
setup_xfail "i*86-univel-sysv4*"
# lynx fails with "next" acting like "continue"
setup_xfail "*-*-*lynx*"
# linux (aout versions) also fails with "next" acting like "continue"
# this is probably more dependant on the kernel version than on the
# object file format or utils. (sigh)
setup_xfail "i*86-*-linuxaout" "i*86-*-linuxoldld"
send "next\n"
expect {
-re "alarm .*$prompt $" { pass "next to 2nd alarm (1)" }
-re "Program received signal SIGTRAP.*first.*$prompt $" {
# This can happen on machines that have a trace flag
# in their PS register.
# The trace flag in the PS register will be set due to
# the `next' command.
# Before calling the signal handler, the PS register
# is pushed along with the context on the user stack.
# When the signal handler has finished, it reenters the
# the kernel via a sigreturn syscall, which restores the
# PS register along with the context.
# If the kernel erroneously does not clear the trace flag
# in the pushed context, gdb will receive a SIGTRAP from
# the set trace flag in the restored context after the
# signal handler has finished.
# I do not yet understand why the SIGTRAP does not occur
# after stepping the instruction at the restored PC on
# i386 BSDI 1.0 systems.
# Note that the vax under Ultrix also exhibits
# this behaviour (it is uncovered by the `continue from
# a break in a signal handler' test below).
# With this test the failure is shadowed by hitting the
# through_sigtramp_breakpoint upon return from the signal
# handler.
fail "next to 2nd alarm (1) (probably kernel bug)"
gdb_test "next" "alarm.*" "next to 2nd alarm (1)"
}
-re "Program exited with code.*$prompt $" {
# This is apparently a bug in the UnixWare kernel (but
# has not been investigated beyond the
# resume/target_wait level, and has not been reported
# to Univel). If it steps when a signal is pending,
# it does a continue instead. I don't know whether
# there is a workaround.
# Perhaps this problem exists on other SVR4 systems;
# but (a) we have no reason to think so, and (b) if we
# put a wrong xfail here, we never get an XPASS to let
# us know that it was incorrect (and then if such a
# configuration regresses we have no way of knowing).
# Solaris is not a relevant data point either way
# because it lacks single stepping.
# fnf: I don't agree with the above philosophy. We
# can never be sure that any particular XFAIL is
# specified 100% correctly in that no systems with
# the bug are missed and all systems without the bug
# are excluded. If we include an XFAIL that isn't
# appropriate for a particular system, then when that
# system gets tested it will XPASS, and someone should
# investigate and fix the setup_xfail as appropriate,
# or more preferably, the actual bug. Each such case
# adds more data to narrowing down the scope of the
# problem and ultimately fixing it.
setup_xfail "i*86-*-sysv4*"
fail "'next' behaved as 'continue (known SVR4 bug)'"
return 0
}
-re ".*$prompt $" { fail "next to 2nd alarm (1)" }
timeout { fail "next to 2nd alarm (1); (timeout)" }
eof { fail "next to 2nd alarm (1); (eof)" }
}
gdb_test "break handler" "Breakpoint \[0-9\]+ .*"
gdb_test "next" "\\+\\+count; /\\* second \\*/" \
"next to 2nd ++count in signals_tests_1"
# An alarm has been signaled, give the signal time to get delivered.
exec sleep 2
set bash_bug 0
send "next\n"
setup_xfail "i*86-*-linux"
expect {
-re "Breakpoint.*handler.*$prompt $" {
pass "next to handler in signals_tests_1"
}
-re "Program received signal SIGEMT.*$prompt $" {
# Bash versions before 1.13.5 cause this behaviour
# by blocking SIGTRAP.
fail "next to handler in signals_tests_1 (known problem with bash versions before 1.13.5)"
set bash_bug 1
gdb_test "signal 0" "Breakpoint.*handler.*"
}
-re ".*$prompt $" { fail "next to handler in signals_tests_1" }
timeout { fail "next to handler in signals_tests_1 (timeout)" }
eof { fail "next to handler in signals_tests_1 (eof)" }
}
# This doesn't test that main is frame #2, just that main is frame
# #2, #3, or higher. At some point this should be fixed (but
# it quite possibly would introduce new FAILs on some systems).
setup_xfail "i*86-*-linux" "i*86-*-bsdi2.0"
gdb_test "backtrace" "#0.*handler.*#1.*#2.*main.*" \
"backtrace in signals_tests_1"
gdb_test "break func1" "Breakpoint \[0-9\]+ .*"
gdb_test "break func2" "Breakpoint \[0-9\]+ .*"
# Vax Ultrix and i386 BSD currently fail the next test with
# a SIGTRAP, but with different symptoms.
setup_xfail "vax-*-ultrix*"
setup_xfail "i*86-*-bsd*"
setup_xfail "i*86-*-linux"
send "continue\n"
expect {
-re "Breakpoint.*func1.*$prompt $" { pass "continue to func1" }
-re "Program received signal SIGTRAP.*second.*$prompt $" {
# See explanation for `next to 2nd alarm (1)' fail above.
# We did step into the signal handler, hit a breakpoint
# in the handler and continued from the breakpoint.
# The set trace flag in the restored context is causing
# the SIGTRAP, without stepping an instruction.
fail "continue to func1 (probably kernel bug)"
gdb_test "continue" "Breakpoint.*func1.*" \
"extra continue to func1"
}
-re "Program received signal SIGTRAP.*func1 ..;.*$prompt $" {
# On the vax under Ultrix the set trace flag in the restored
# context is causing the SIGTRAP, but after stepping one
# instruction, as expected.
fail "continue to func1 (probably kernel bug)"
gdb_test "continue" "Breakpoint.*func1.*" \
"extra continue to func1"
}
-re ".*$prompt $" { fail "continue to func1" }
default { fail "continue to func1" }
}
setup_xfail "*-*-irix*"
setup_xfail "i*86-*-linux"
send "signal SIGUSR1\n"
expect {
-re "Breakpoint.*handler.*$prompt $" { pass "signal SIGUSR1" }
-re "Program received signal SIGUSR1.*$prompt $" {
# This is what irix4 and irix5 do.
# It would appear to be a kernel bug.
fail "signal SIGUSR1"
gdb_test "continue" "Breakpoint.*handler.*" "pass it SIGUSR1"
}
-re ".*$prompt $" { fail "signal SIGUSR1" }
default { fail "signal SIGUSR1" }
}
# Will tend to wrongly require an extra continue.
# The problem here is that the breakpoint at func1 will be
# inserted, and when the system finishes with the signal
# handler it will try to execute there. For GDB to try to
# remember that it was going to step over a breakpoint when a
# signal happened, distinguish this case from the case where
# func1 is called from the signal handler, etc., seems
# exceedingly difficult. So don't expect this to get fixed
# anytime soon.
setup_xfail "*-*-*"
send "continue\n"
expect {
-re "Breakpoint.*func2.*$prompt $" { pass "continue to func2" }
-re "Breakpoint.*func1.*$prompt $" {
fail "continue to func2"
gdb_test "continue" "Breakpoint.*func2.*" \
"extra continue to func2"
}
-re ".*$prompt $" { fail "continue to func2" }
default { fail "continue to func2" }
}
exec sleep 2
# GDB yanks out the breakpoints to step over the breakpoint it
# stopped at, which means the breakpoint at handler is yanked.
# But if NO_SINGLE_STEP, we won't get another chance to reinsert
# them (at least not with procfs, where we tell the kernel not
# to tell gdb about `pass' signals). So the fix would appear to
# be to just yank that one breakpoint when we step over it.
setup_xfail "sparc*-*-*"
setup_xfail "rs6000-*-*"
setup_xfail "powerpc-*-*"
# A faulty bash will not step the inferior into sigtramp on sun3.
if {$bash_bug} then {
setup_xfail "m68*-*-sunos4*"
}
setup_xfail "i*86-*-linux"
gdb_test "continue" "Breakpoint.*handler.*" "continue to handler"
# If the NO_SINGLE_STEP failure happened, we have already exited.
# If we succeeded a continue will return from the handler to func2.
# GDB now has `forgotten' that it intended to step over the
# breakpoint at func2 and will stop at func2.
setup_xfail "*-*-*"
# The sun3 with a faulty bash will also be `forgetful' but it
# already got the spurious stop at func2 and this continue will work.
if {$bash_bug} then {
clear_xfail "m68*-*-sunos4*"
}
gdb_test "continue" "Program exited with code 010\\." \
"continue to exit in signals_tests_1 "
}
}
# On a few losing systems, ptrace (PT_CONTINUE) or ptrace (PT_STEP)
# causes pending signals to be cleared, which causes these tests to
# get nowhere fast. This is totally losing behavior (perhaps there
# are cases in which is it useful but the user needs more control,
# which they mostly have in GDB), but some people apparently think it
# is a feature. It is documented in the ptrace manpage on Motorola
# Delta Series sysV68 R3V7.1 and on HPUX 9.0. Even the non-HPUX PA
# OSes (BSD and OSF/1) seem to have figured they had to copy this
# braindamage.
if {[ istarget "m68*-motorola-*" ] || [ istarget "hppa*-*-bsd*" ] ||
[ istarget "*-*-hpux*" ] || [ istarget "hppa*-*-osf*" ]} then {
setup_xfail "*-*-*"
fail "ptrace loses on signals on this target"
return 0
}
# lynx2.2.2 doesn't lose signals, instead it screws up the stack pointer
# in some of these tests leading to massive problems. I've
# reported this to lynx, hopefully it'll be fixed in lynx2.3.
# Severe braindamage.
if [ istarget "*-*-*lynx*" ] then {
setup_xfail "*-*-*"
fail "kernel scroggs stack pointer in signal tests on this target"
return 0
}
gdb_exit
gdb_start
# This will need to be updated as the exact list of signals changes,
# but I want to test that TARGET_SIGNAL_0, TARGET_SIGNAL_DEFAULT, and
# TARGET_SIGNAL_UNKNOWN are skipped.
# Increase expect input buffer for large output from gdb.
# Allow blank or TAB as whitespace characters and test individually for
# each specific signal.
proc test_handle_all_print {} {
match_max 10000
gdb_test "handle all print" \
"Signal\[ \t\]+Stop\[ \t\]+Print\[ \t\]+Pass to program\[ \t\]+Description\r\n.*" \
"handle all print - Output headers"
gdb_test "handle all print" \
".*SIGHUP\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Hangup\r\n.*" \
"handle all print - Hangup"
gdb_test "handle all print" \
".*SIGQUIT\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Quit\r\n.*" \
"handle all print - Quit"
gdb_test "handle all print" \
".*SIGILL\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Illegal instruction\r\n.*" \
"handle all print - Illegal instruction"
gdb_test "handle all print" \
".*SIGABRT\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Aborted\r\n.*" \
"handle all print - Aborted"
gdb_test "handle all print" \
".*SIGEMT\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Emulation trap\r\n.*" \
"handle all print - Emulation trap"
gdb_test "handle all print" \
".*SIGFPE\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Arithmetic exception\r\n.*" \
"handle all print - Arithmetic exception"
gdb_test "handle all print" \
".*SIGKILL\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Killed\r\n.*" \
"handle all print - Killed"
gdb_test "handle all print" \
".*SIGBUS\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Bus error\r\n.*" \
"handle all print - Bus error"
gdb_test "handle all print" \
".*SIGSEGV\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Segmentation fault\r\n.*" \
"handle all print - Segmentation fault"
gdb_test "handle all print" \
".*SIGSYS\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Bad system call\r\n.*" \
"handle all print - Bad system call"
gdb_test "handle all print" \
".*SIGPIPE\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Broken pipe\r\n.*" \
"handle all print - Broken pipe"
gdb_test "handle all print" \
".*SIGALRM\[ \t\]+No\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Alarm clock\r\n.*" \
"handle all print - Alarm clock"
gdb_test "handle all print" \
".*SIGTERM\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Terminated\r\n.*" \
"handle all print - Terminated"
gdb_test "handle all print" \
".*SIGURG\[ \t\]+No\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Urgent I/O condition\r\n.*" \
"handle all print - Urgent I/O condition"
gdb_test "handle all print" \
".*SIGSTOP\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Stopped \\(signal\\)\r\n.*" \
"handle all print - Stopped (signal)"
gdb_test "handle all print" \
".*SIGTSTP\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Stopped \\(user\\)\r\n.*" \
"handle all print - Stopped (user)"
gdb_test "handle all print" \
".*SIGCONT\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Continued\r\n.*" \
"handle all print - Continued"
gdb_test "handle all print" \
".*SIGCHLD\[ \t\]+No\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Child status changed\r\n.*" \
"handle all print - Child status changed"
gdb_test "handle all print" \
".*SIGTTIN\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Stopped \\(tty input\\)\r\n.*" \
"handle all print - Stopped (tty input)"
gdb_test "handle all print" \
".*SIGTTOU\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Stopped \\(tty output\\)\r\n.*" \
"handle all print - Stopped (tty output)"
gdb_test "handle all print" \
".*SIGIO\[ \t\]+No\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+I/O possible\r\n.*" \
"handle all print - I/O possible"
gdb_test "handle all print" \
".*SIGXCPU\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+CPU time limit exceeded\r\n.*" \
"handle all print - CPU time limit exceeded"
gdb_test "handle all print" \
".*SIGXFSZ\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+File size limit exceeded\r\n.*" \
"handle all print - File size limit exceeded"
gdb_test "handle all print" \
".*SIGVTALRM\[ \t\]+No\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Virtual timer expired\r\n.*" \
"handle all print - Virtual timer expired"
gdb_test "handle all print" \
".*SIGPROF\[ \t\]+No\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Profiling timer expired\r\n.*" \
"handle all print - Profiling timer expired"
gdb_test "handle all print" \
".*SIGWINCH\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Window size changed\r\n.*" \
"handle all print - Window size changed"
gdb_test "handle all print" \
".*SIGLOST\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Resource lost\r\n.*" \
"handle all print - Resource lost"
gdb_test "handle all print" \
".*SIGUSR1\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+User defined signal 1\r\n.*" \
"handle all print - User defined signal 1"
gdb_test "handle all print" \
".*SIGUSR2\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+User defined signal 2\r\n.*" \
"handle all print - User defined signal 2"
gdb_test "handle all print" \
".*SIGPWR\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Power fail/restart\r\n.*" \
"handle all print - Power fail/restart"
gdb_test "handle all print" \
".*SIGPOLL\[ \t\]+No\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Pollable event occurred\r\n.*" \
"handle all print - Pollable event occurred"
gdb_test "handle all print" \
".*SIGWIND\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+SIGWIND\r\n.*" \
"handle all print - SIGWIND"
gdb_test "handle all print" \
".*SIGPHONE\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+SIGPHONE\r\n.*" \
"handle all print - SIGPHONE"
gdb_test "handle all print" \
".*SIGWAITING\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Process's LWPs are blocked\r\n.*" \
"handle all print - Process's LWPs are blocked"
gdb_test "handle all print" \
".*SIGLWP\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Signal LWP\r\n.*" \
"handle all print - Signal LWP"
gdb_test "handle all print" \
".*SIGDANGER\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Swap space dangerously low\r\n.*" \
"handle all print - Swap space dangerously low"
gdb_test "handle all print" \
".*SIGGRANT\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Monitor mode granted\r\n.*" \
"handle all print - Monitor mode granted"
gdb_test "handle all print" \
".*SIGRETRACT\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Need to relinguish monitor mode\r\n.*" \
"handle all print - Need to relinguish monitor mode"
gdb_test "handle all print" \
".*SIGMSG\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Monitor mode data available\r\n.*" \
"handle all print - Monitor mode data available"
gdb_test "handle all print" \
".*SIGSOUND\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Sound completed\r\n.*" \
"handle all print - Sound completed"
gdb_test "handle all print" \
".*SIGSAK\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Secure attention\r\n.*" \
"handle all print - Secure attention"
gdb_test "handle all print" \
".*SIGPRIO\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+SIGPRIO\r\n.*" \
"handle all print - SIGPRIO"
gdb_test "handle all print" \
".*SIG33\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 33\r\n.*" \
"handle all print - Real-time event 33"
gdb_test "handle all print" \
".*SIG34\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 34\r\n.*" \
"handle all print - Real-time event 34"
gdb_test "handle all print" \
".*SIG35\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 35\r\n.*" \
"handle all print - Real-time event 35"
gdb_test "handle all print" \
".*SIG36\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 36\r\n.*" \
"handle all print - Real-time event 36"
gdb_test "handle all print" \
".*SIG37\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 37\r\n.*" \
"handle all print - Real-time event 37"
gdb_test "handle all print" \
".*SIG38\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 38\r\n.*" \
"handle all print - Real-time event 38"
gdb_test "handle all print" \
".*SIG39\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 39\r\n.*" \
"handle all print - Real-time event 39"
gdb_test "handle all print" \
".*SIG40\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 40\r\n.*" \
"handle all print - Real-time event 40"
gdb_test "handle all print" \
".*SIG41\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 41\r\n.*" \
"handle all print - Real-time event 41"
gdb_test "handle all print" \
".*SIG42\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 42\r\n.*" \
"handle all print - Real-time event 42"
gdb_test "handle all print" \
".*SIG43\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 43\r\n.*" \
"handle all print - Real-time event 43"
gdb_test "handle all print" \
".*SIG44\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 44\r\n.*" \
"handle all print - Real-time event 44"
gdb_test "handle all print" \
".*SIG45\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 45\r\n.*" \
"handle all print - Real-time event 45"
gdb_test "handle all print" \
".*SIG46\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 46\r\n.*" \
"handle all print - Real-time event 46"
gdb_test "handle all print" \
".*SIG47\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 47\r\n.*" \
"handle all print - Real-time event 47"
gdb_test "handle all print" \
".*SIG48\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 48\r\n.*" \
"handle all print - Real-time event 48"
gdb_test "handle all print" \
".*SIG49\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 49\r\n.*" \
"handle all print - Real-time event 49"
gdb_test "handle all print" \
".*SIG50\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 50\r\n.*" \
"handle all print - Real-time event 50"
gdb_test "handle all print" \
".*SIG51\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 51\r\n.*" \
"handle all print - Real-time event 51"
gdb_test "handle all print" \
".*SIG52\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 52\r\n.*" \
"handle all print - Real-time event 52"
gdb_test "handle all print" \
".*SIG53\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 53\r\n.*" \
"handle all print - Real-time event 53"
gdb_test "handle all print" \
".*SIG54\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 54\r\n.*" \
"handle all print - Real-time event 54"
gdb_test "handle all print" \
".*SIG55\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 55\r\n.*" \
"handle all print - Real-time event 55"
gdb_test "handle all print" \
".*SIG56\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 56\r\n.*" \
"handle all print - Real-time event 56"
gdb_test "handle all print" \
".*SIG57\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 57\r\n.*" \
"handle all print - Real-time event 57"
gdb_test "handle all print" \
".*SIG58\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 58\r\n.*" \
"handle all print - Real-time event 58"
gdb_test "handle all print" \
".*SIG59\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 59\r\n.*" \
"handle all print - Real-time event 59"
gdb_test "handle all print" \
".*SIG60\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 60\r\n.*" \
"handle all print - Real-time event 60"
gdb_test "handle all print" \
".*SIG61\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 61\r\n.*" \
"handle all print - Real-time event 61"
gdb_test "handle all print" \
".*SIG62\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 62\r\n.*" \
"handle all print - Real-time event 62"
gdb_test "handle all print" \
".*SIG63\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Real-time event 63\r\n.*" \
"handle all print - Real-time event 63"
gdb_test "handle all print" \
".*EXC_BAD_ACCESS\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Could not access memory\r\n.*" \
"handle all print - Could not access memory"
gdb_test "handle all print" \
".*EXC_BAD_INSTRUCTION\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Illegal instruction/operand\r\n.*" \
"handle all print - Illegal instruction/operand"
gdb_test "handle all print" \
".*EXC_ARITHMETIC\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Arithmetic exception\r\n.*" \
"handle all print - Arithmetic exception"
gdb_test "handle all print" \
".*EXC_EMULATION\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Emulation instruction\r\n.*" \
"handle all print - Emulation instruction"
gdb_test "handle all print" \
".*EXC_SOFTWARE\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Software generated exception\r\n.*" \
"handle all print - Software generated exception"
gdb_test "handle all print" \
".*EXC_BREAKPOINT\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Yes\[ \t\]+Breakpoint.*" \
"handle all print - Breakpoint"
}
test_handle_all_print
gdb_exit
gdb_start
gdb_reinitialize_dir $srcdir/$subdir
gdb_load $binfile
signal_tests_1
# Force a resync, so we're looking at the right prompt. On SCO we
# were getting out of sync (I don't understand why).
send "p 1+1\n"
expect {
-re "= 2.*$prompt $" {}
-re ".*$prompt $" { perror "sync trouble in signals.exp" }
default { perror "sync trouble in signals.exp" }
}
if [runto_main] then {
gdb_test "break handler if 0" "Breakpoint \[0-9\]+ .*"
gdb_test "set \$handler_breakpoint_number = \$bpnum" ""
# Get to the point where a signal is waiting to be delivered
gdb_test "next" "signal \\(SIGUSR1.*" "next to signal in signals.exp"
gdb_test "next" "alarm \\(.*" "next to alarm #1 in signals.exp"
gdb_test "next" "\\+\\+count; /\\* first \\*/" \
"next to ++count #1 in signals.exp"
# Give the signal time to get delivered
exec sleep 2
# Now call a function. When GDB tries to run the stack dummy,
# it will hit the breakpoint at handler. Provided it doesn't
# lose its cool, this is not a problem, it just has to note
# that the breakpoint condition is false and keep going.
gdb_test "p func1 ()" "^p func1 \\(\\)\r\n.\[0-9\]* = void" \
"p func1 () #1 in signals.exp"
# Make sure the count got incremented.
# Haven't investigated this xfail
setup_xfail "rs6000-*-*"
setup_xfail "powerpc-*-*"
gdb_test "p count" "= 2" "p count #1 in signals.exp"
if { [istarget "rs6000-*-*"] || [istarget "powerpc-*-*"] } { return 0 }
gdb_test "condition \$handler_breakpoint_number" "now unconditional\\."
gdb_test "next" "alarm \\(.*" "next to alarm #2 in signals.exp"
gdb_test "next" "\\+\\+count; /\\* second \\*/" \
"next to ++count #2 in signals.exp"
exec sleep 2
# This time we stop when GDB tries to run the stack dummy.
# So it is OK that we do not print the return value from the function.
gdb_test "p func1 ()" \
"Breakpoint \[0-9\]*, handler.*
The program being debugged stopped while in a function called from GDB.*" \
"p func1 () #2 in signals.exp"
# But we should be able to backtrace...
# On alpha-*-osf2.0 this test works when run manually but sometime fails when
# run under dejagnu, making it very hard to debug the problem. Weird...
gdb_test "bt" "#0.*handler.*#1.*#2.*main.*" "bt in signals.exp"
# ...and continue...
gdb_test "continue" "Continuing\\." "continue in signals.exp"
# ...and then count should have been incremented
gdb_test "p count" "= 5" "p count #2 in signals.exp"
}
return 0