1 # Copyright 2004, 2005, 2006, 2007 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 "Could not insert single-step breakpoint.*$gdb_prompt $" {
83 setup_kfail "sparc*-*-openbsd*" gdb/1736
84 fail "$test (could not insert single-step breakpoint)"
86 -re "done = 1;.*${gdb_prompt} $" {
88 exp_continue -continue_timer
90 -re "\} .. handler .*${gdb_prompt} $" {
92 exp_continue -continue_timer
94 -re "Program exited normally.*${gdb_prompt} $" {
95 setup_kfail powerpc-*-*bsd* gdb/1639
96 fail "$test (program exited)"
98 -re "(while ..done|done = 0).*${gdb_prompt} $" {
99 # After stepping out of a function /r signal-handler, GDB will
100 # advance the inferior until it is at the first instruction of
101 # a code-line. While typically things return to the middle of
102 # the "while..." (and hence GDB advances the inferior to the
103 # "return..." line) it is also possible for the return to land
104 # on the first instruction of "while...". Accept both cases.
110 proc advancei { i } {
112 set prefix "$i from handleri"
115 # Get us back into the handler
116 gdb_test "continue" ".* handler .*" "$prefix; continue to handler"
118 set test "$prefix; leave handler"
119 gdb_test_multiple "$i" "${test}" {
120 -re "Cannot insert breakpoint 0.*${gdb_prompt} $" {
121 # Some platforms use a special read-only page for signal
122 # trampolines. We can't set a breakpoint there, and we
123 # don't gracefully fall back to single-stepping.
124 setup_kfail "i?86-*-linux*" gdb/1736
125 setup_kfail "*-*-openbsd*" gdb/1736
126 fail "$test (could not set breakpoint)"
129 -re "Could not insert single-step breakpoint.*$gdb_prompt $" {
130 setup_kfail "sparc*-*-openbsd*" gdb/1736
131 fail "$test (could not insert single-step breakpoint)"
133 -re "Breakpoint \[0-9\]*, handler .*${gdb_prompt} $" {
134 fail "$test (hit breakpoint again)"
136 -re "done = 1;.*${gdb_prompt} $" {
138 exp_continue -continue_timer
140 -re "\} .. handler .*${gdb_prompt} $" {
142 exp_continue -continue_timer
144 -re "signal handler called.*${gdb_prompt} $" {
147 -re "main .*${gdb_prompt} $" {
148 fail "$test (in main)"
150 -re "Program exited normally.*${gdb_prompt} $" {
151 fail "$test (program exited)"
154 -re "Make handler return now.*y or n. $" {
156 exp_continue -continue_timer
160 set test "$prefix; leave signal trampoline"
161 gdb_test_multiple "$i" "${test}" {
162 -re "while .*${gdb_prompt} $" {
163 pass "$test (in main)"
165 -re "signal handler called.*${gdb_prompt} $" {
167 exp_continue -continue_timer
169 -re "return .*${gdb_prompt} $" {
170 fail "$test (stepped)"
172 -re "Make .*frame return now.*y or n. $" {
174 exp_continue -continue_timer
176 -re "Program exited normally.*${gdb_prompt} $" {
177 kfail gdb/1639 "$test (program exited)"
180 -re "The program is not being run.*${gdb_prompt} $" {
181 if { $program_exited } {
182 # Previously kfailed with an exit
183 pass "$test (the program is not being run)"
185 fail "$test (the program is not being run)"
191 # Check that we can step/next our way out of a signal handler.
201 gdb_test "set done = 1" "" "Set done as return will have skipped it"
204 # Check that we can step/next our way into / over a signal handler.
206 # There are at least the following cases: breakpoint @pc VS breakpoint
207 # in handler VS step / next / continue.
209 # Use the real-time itimer, as otherwize the process never gets enough
210 # time to expire the timer.
213 set infinite_loop [gdb_get_line_number {while (!done)}]
214 gdb_test "set itimer = itimer_real"
215 gdb_test "break [gdb_get_line_number {done = 0}]"
217 # Try stepping when there's a signal pending, and a breakpoint at the
218 # handler. Should step into the signal handler.
220 proc skip_to_handler { i } {
223 set prefix "$i to handler"
225 # Run around to the done
226 # You can add more patterns to this if you need them.
227 set test "$prefix; resync"
228 gdb_test_multiple "continue" "$test" {
229 -re "done = 0.*$gdb_prompt " {
234 # Advance to the infinite loop
235 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
237 # Make the signal pending
240 # Insert / remove the handler breakpoint.
241 gdb_test "break handler" "" "$prefix; break handler"
242 gdb_test "$i" " handler .*" "$prefix; performing $i"
243 gdb_test "clear handler" "" "$prefix; clear handler"
248 skip_to_handler continue
250 # Try stepping when there's a signal pending, and a breakpoint at the
251 # handler's entry-point. Should step into the signal handler stopping
252 # at the entry-point.
254 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
255 # signal, resume the process at the first instruction of the signal
256 # handler and not the first instruction of the signal trampoline. The
257 # stack is constructed such that the signal handler still appears to
258 # have been called by the trampoline code. This test checks that it
259 # is possible to stop the inferior, even at that first instruction.
261 proc skip_to_handler_entry { i } {
264 set prefix "$i to handler entry"
266 # Run around to the done
267 # You can add more patterns to this if you need them.
268 set test "$prefix; resync"
269 gdb_test_multiple "continue" "$test" {
270 -re "done = 0.*$gdb_prompt " {
275 # Advance to the infinite loop
276 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
278 # Make the signal pending
281 # Insert / remove the handler breakpoint.
282 gdb_test "break *handler" "" "$prefix; break handler"
283 gdb_test "$i" " handler .*" "$prefix; performing $i"
284 gdb_test "clear *handler" "" "$prefix; clear handler"
287 skip_to_handler_entry step
288 skip_to_handler_entry next
289 skip_to_handler_entry continue
291 # Try stepping when there's a signal pending but no breakpoints.
292 # Should skip the handler advancing to the next line.
294 proc skip_over_handler { i } {
297 set prefix "$i over handler"
299 # Run around to the done
300 # You can add more patterns to this if you need them.
301 set test "$prefix; resync"
302 gdb_test_multiple "continue" "$test" {
303 -re "done = 0.*$gdb_prompt " {
308 # Advance to the infinite loop
309 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
311 # Make the signal pending
314 gdb_test "$i" "done = 0.*" "$prefix; performing $i"
317 skip_over_handler step
318 skip_over_handler next
319 skip_over_handler continue
321 # Try stepping when there's a signal pending, a pre-existing
322 # breakpoint at the current instruction, and a breakpoint in the
323 # handler. Should advance to the signal handler.
325 proc breakpoint_to_handler { i } {
328 set prefix "$i on breakpoint, to handler"
330 # Run around to the done
331 # You can add more patterns to this if you need them.
332 set test "$prefix; resync"
333 gdb_test_multiple "continue" "$test" {
334 -re "done = 0.*$gdb_prompt " {
339 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
340 gdb_test "break handler" "" "$prefix; break handler"
342 # Continue to the infinite loop
343 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
345 # Make the signal pending
348 setup_kfail "i*86-*-*" gdb/1738
349 gdb_test "$i" " handler .*" "$prefix; performing $i"
350 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
351 gdb_test "clear handler" "" "$prefix; clear handler"
354 breakpoint_to_handler step
355 breakpoint_to_handler next
356 breakpoint_to_handler continue
358 # Try stepping when there's a signal pending, and a breakpoint at the
359 # handler's entry instruction and a breakpoint at the current
360 # instruction. Should step into the signal handler and breakpoint at
361 # that entry instruction.
363 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
364 # signal, resume the process at the first instruction of the signal
365 # handler and not the first instruction of the signal trampoline. The
366 # stack is constructed such that the signal handler still appears to
367 # have been called by the trampoline code. This test checks that it
368 # is possible to stop the inferior, even at that first instruction.
370 proc breakpoint_to_handler_entry { i } {
373 set prefix "$i on breakpoint, to handler entry"
375 # Run around to the done
376 # You can add more patterns to this if you need them.
377 set test "$prefix; resync"
378 gdb_test_multiple "continue" "$test" {
379 -re "done = 0.*$gdb_prompt " {
384 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
385 gdb_test "break *handler" "" "$prefix; break handler"
387 # Continue to the infinite loop
388 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
390 # Make the signal pending
393 setup_kfail "i*86-*-*" gdb/1738
394 gdb_test "$i" " handler .*" "$prefix; performing $i"
395 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
396 gdb_test "clear *handler" "" "$prefix; clear handler"
399 breakpoint_to_handler_entry step
400 breakpoint_to_handler_entry next
401 breakpoint_to_handler_entry continue
403 # Try stepping when there's a signal pending, and a pre-existing
404 # breakpoint at the current instruction, and no breakpoint in the
405 # handler. Should advance to the next line.
407 proc breakpoint_over_handler { i } {
410 set prefix "$i on breakpoint, skip handler"
412 # Run around to the done
413 # You can add more patterns to this if you need them.
414 set test "$prefix; resync"
415 gdb_test_multiple "continue" "$test" {
416 -re "done = 0.*$gdb_prompt " {
421 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
423 # Continue to the infinite loop
424 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
426 # Make the signal pending
429 gdb_test "$i" "done = 0.*" "$prefix; performing $i"
430 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
433 breakpoint_over_handler step
434 breakpoint_over_handler next
435 breakpoint_over_handler continue