1 # Copyright 2004 Free Software Foundation, Inc.
3 # This program is free software; you can redistribute it and/or modify
4 # it under the terms of the GNU General Public License as published by
5 # the Free Software Foundation; either version 2 of the License, or
6 # (at your option) any later version.
8 # This program is distributed in the hope that it will be useful,
9 # but WITHOUT ANY WARRANTY; without even the implied warranty of
10 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
11 # GNU General Public License for more details.
13 # You should have received a copy of the GNU General Public License
14 # along with this program; if not, write to the Free Software
15 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
18 # The program sigstep.c creates a very simple backtrace containing one
19 # signal handler and signal trampoline. A flag is set and then the
20 # handler returns. This is repeated at infinitum.
22 # This test runs the program up to the signal handler, and then
23 # attempts to step/next out of the handler and back into main.
25 if [target_info exists gdb,nosignals] {
26 verbose "Skipping sigstep.exp because of nosignals."
38 set srcfile ${testfile}.c
39 set binfile ${objdir}/${subdir}/${testfile}
40 if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
41 untested "Couldn't compile ${module}.c"
48 gdb_reinitialize_dir $srcdir/$subdir
51 gdb_test "display/i \$pc"
54 if { ![runto_main] } then {
58 # Pass all the alarms straight through (but verbosely)
59 # gdb_test "handle SIGALRM print pass nostop"
60 # gdb_test "handle SIGVTALRM print pass nostop"
61 # gdb_test "handle SIGPROF print pass nostop"
63 # Run to the signal handler, validate the backtrace.
64 gdb_test "break handler"
65 gdb_test "continue" ".* handler .*" "continue to stepi handler"
67 gdb_expect_list "backtrace for nexti" ".*$gdb_prompt $" {
68 "\[\r\n\]+.0 \[^\r\n\]* handler "
69 "\[\r\n\]+.1 .signal handler called."
70 "\[\r\n\]+.2 \[^\r\n\]* main .*"
75 set prefix "$i from handler"
77 # Get us back into the handler
78 gdb_test "continue" ".* handler .*" "$prefix; continue to handler"
80 set test "$prefix; leave handler"
81 gdb_test_multiple "$i" "${test}" {
82 -re "done = 1;.*${gdb_prompt} $" {
84 exp_continue -continue_timer
86 -re "\} .. handler .*${gdb_prompt} $" {
88 exp_continue -continue_timer
90 -re "Program exited normally.*${gdb_prompt} $" {
91 setup_kfail powerpc-*-*bsd* gdb/1639
92 fail "$test (program exited)"
94 -re "(while ..done|done = 0).*${gdb_prompt} $" {
95 # After stepping out of a function /r signal-handler, GDB will
96 # advance the inferior until it is at the first instruction of
97 # a code-line. While typically things return to the middle of
98 # the "while..." (and hence GDB advances the inferior to the
99 # "return..." line) it is also possible for the return to land
100 # on the first instruction of "while...". Accept both cases.
106 proc advancei { i } {
108 set prefix "$i from handleri"
111 # Get us back into the handler
112 gdb_test "continue" ".* handler .*" "$prefix; continue to handler"
114 set test "$prefix; leave handler"
115 gdb_test_multiple "$i" "${test}" {
116 -re "Cannot insert breakpoint 0.*${gdb_prompt} $" {
117 # Some platforms use a special read-only page for signal
118 # trampolines. We can't set a breakpoint there, and we
119 # don't gracefully fall back to single-stepping.
120 setup_kfail "i?86-*-linux*" gdb/1736
121 setup_kfail "*-*-openbsd*" gdb/1736
122 fail "$test (could not set breakpoint)"
125 -re "done = 1;.*${gdb_prompt} $" {
127 exp_continue -continue_timer
129 -re "\} .. handler .*${gdb_prompt} $" {
131 exp_continue -continue_timer
133 -re "signal handler called.*${gdb_prompt} $" {
136 -re "main .*${gdb_prompt} $" {
137 fail "$test (in main)"
139 -re "Program exited normally.*${gdb_prompt} $" {
140 fail "$test (program exited)"
143 -re "Make handler return now.*y or n. $" {
145 exp_continue -continue_timer
149 set test "$prefix; leave signal trampoline"
150 gdb_test_multiple "$i" "${test}" {
151 -re "while .*${gdb_prompt} $" {
152 pass "$test (in main)"
154 -re "signal handler called.*${gdb_prompt} $" {
156 exp_continue -continue_timer
158 -re "return .*${gdb_prompt} $" {
159 fail "$test (stepped)"
161 -re "Make .*frame return now.*y or n. $" {
163 exp_continue -continue_timer
165 -re "Program exited normally.*${gdb_prompt} $" {
166 kfail gdb/1639 "$test (program exited)"
169 -re "The program is not being run.*${gdb_prompt} $" {
170 if { $program_exited } {
171 # Previously kfailed with an exit
172 pass "$test (the program is not being run)"
174 fail "$test (the program is not being run)"
180 # Check that we can step/next our way out of a signal handler.
190 gdb_test "set done = 1" "" "Set done as return will have skipped it"
193 # Check that we can step/next our way into / over a signal handler.
195 # There are at least the following cases: breakpoint @pc VS breakpoint
196 # in handler VS step / next / continue.
198 # Use the real-time itimer, as otherwize the process never gets enough
199 # time to expire the timer.
202 set infinite_loop [gdb_get_line_number {while (!done)}]
203 gdb_test "set itimer = itimer_real"
204 gdb_test "break [gdb_get_line_number {done = 0}]"
206 # Try stepping when there's a signal pending, and a breakpoint at the
207 # handler. Should step into the signal handler.
209 proc skip_to_handler { i } {
212 set prefix "$i to handler"
214 # Run around to the done
215 # You can add more patterns to this if you need them.
216 set test "$prefix; resync"
217 gdb_test_multiple "continue" "$test" {
218 -re "done = 0.*$gdb_prompt " {
223 # Advance to the infinite loop
224 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
226 # Make the signal pending
229 # Insert / remove the handler breakpoint.
230 gdb_test "break handler" "" "$prefix; break handler"
231 gdb_test "$i" " handler .*" "$prefix; performing $i"
232 gdb_test "clear handler" "" "$prefix; clear handler"
237 skip_to_handler continue
239 # Try stepping when there's a signal pending, and a breakpoint at the
240 # handler's entry-point. Should step into the signal handler stopping
241 # at the entry-point.
243 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
244 # signal, resume the process at the first instruction of the signal
245 # handler and not the first instruction of the signal trampoline. The
246 # stack is constructed such that the signal handler still appears to
247 # have been called by the trampoline code. This test checks that it
248 # is possible to stop the inferior, even at that first instruction.
250 proc skip_to_handler_entry { i } {
253 set prefix "$i to handler entry"
255 # Run around to the done
256 # You can add more patterns to this if you need them.
257 set test "$prefix; resync"
258 gdb_test_multiple "continue" "$test" {
259 -re "done = 0.*$gdb_prompt " {
264 # Advance to the infinite loop
265 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
267 # Make the signal pending
270 # Insert / remove the handler breakpoint.
271 gdb_test "break *handler" "" "$prefix; break handler"
272 gdb_test "$i" " handler .*" "$prefix; performing $i"
273 gdb_test "clear *handler" "" "$prefix; clear handler"
276 skip_to_handler_entry step
277 skip_to_handler_entry next
278 skip_to_handler_entry continue
280 # Try stepping when there's a signal pending but no breakpoints.
281 # Should skip the handler advancing to the next line.
283 proc skip_over_handler { i } {
286 set prefix "$i over handler"
288 # Run around to the done
289 # You can add more patterns to this if you need them.
290 set test "$prefix; resync"
291 gdb_test_multiple "continue" "$test" {
292 -re "done = 0.*$gdb_prompt " {
297 # Advance to the infinite loop
298 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
300 # Make the signal pending
303 gdb_test "$i" "done = 0.*" "$prefix; performing $i"
306 skip_over_handler step
307 skip_over_handler next
308 skip_over_handler continue
310 # Try stepping when there's a signal pending, a pre-existing
311 # breakpoint at the current instruction, and a breakpoint in the
312 # handler. Should advance to the signal handler.
314 proc breakpoint_to_handler { i } {
317 set prefix "$i on breakpoint, to handler"
319 # Run around to the done
320 # You can add more patterns to this if you need them.
321 set test "$prefix; resync"
322 gdb_test_multiple "continue" "$test" {
323 -re "done = 0.*$gdb_prompt " {
328 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
329 gdb_test "break handler" "" "$prefix; break handler"
331 # Continue to the infinite loop
332 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
334 # Make the signal pending
337 setup_kfail "i*86-*-*" gdb/1738
338 gdb_test "$i" " handler .*" "$prefix; performing $i"
339 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
340 gdb_test "clear handler" "" "$prefix; clear handler"
343 breakpoint_to_handler step
344 breakpoint_to_handler next
345 breakpoint_to_handler continue
347 # Try stepping when there's a signal pending, and a breakpoint at the
348 # handler's entry instruction and a breakpoint at the current
349 # instruction. Should step into the signal handler and breakpoint at
350 # that entry instruction.
352 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
353 # signal, resume the process at the first instruction of the signal
354 # handler and not the first instruction of the signal trampoline. The
355 # stack is constructed such that the signal handler still appears to
356 # have been called by the trampoline code. This test checks that it
357 # is possible to stop the inferior, even at that first instruction.
359 proc breakpoint_to_handler_entry { i } {
362 set prefix "$i on breakpoint, to handler entry"
364 # Run around to the done
365 # You can add more patterns to this if you need them.
366 set test "$prefix; resync"
367 gdb_test_multiple "continue" "$test" {
368 -re "done = 0.*$gdb_prompt " {
373 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
374 gdb_test "break *handler" "" "$prefix; break handler"
376 # Continue to the infinite loop
377 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
379 # Make the signal pending
382 setup_kfail "i*86-*-*" gdb/1738
383 gdb_test "$i" " handler .*" "$prefix; performing $i"
384 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
385 gdb_test "clear *handler" "" "$prefix; clear handler"
388 breakpoint_to_handler_entry step
389 breakpoint_to_handler_entry next
390 breakpoint_to_handler_entry continue
392 # Try stepping when there's a signal pending, and a pre-existing
393 # breakpoint at the current instruction, and no breakpoint in the
394 # handler. Should advance to the next line.
396 proc breakpoint_over_handler { i } {
399 set prefix "$i on breakpoint, skip handler"
401 # Run around to the done
402 # You can add more patterns to this if you need them.
403 set test "$prefix; resync"
404 gdb_test_multiple "continue" "$test" {
405 -re "done = 0.*$gdb_prompt " {
410 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
412 # Continue to the infinite loop
413 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
415 # Make the signal pending
418 gdb_test "$i" "done = 0.*" "$prefix; performing $i"
419 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
422 breakpoint_over_handler step
423 breakpoint_over_handler next
424 breakpoint_over_handler continue