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} $" {
86 -re "\} .. handler .*${gdb_prompt} $" {
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 fail "$test (could not set breakpoint)"
124 -re "done = 1;.*${gdb_prompt} $" {
128 -re "\} .. handler .*${gdb_prompt} $" {
132 -re "signal handler called.*${gdb_prompt} $" {
135 -re "main .*${gdb_prompt} $" {
136 fail "$test (in main)"
138 -re "Program exited normally.*${gdb_prompt} $" {
139 fail "$test (program exited)"
142 -re "Make handler return now.*y or n. $" {
148 set test "$prefix; leave signal trampoline"
149 gdb_test_multiple "$i" "${test}" {
150 -re "while .*${gdb_prompt} $" {
151 pass "$test (in main)"
153 -re "signal handler called.*${gdb_prompt} $" {
157 -re "return .*${gdb_prompt} $" {
158 fail "$test (stepped)"
160 -re "Make .*frame return now.*y or n. $" {
164 -re "Program exited normally.*${gdb_prompt} $" {
165 kfail gdb/1639 "$test (program exited)"
168 -re "The program is not being run.*${gdb_prompt} $" {
169 if { $program_exited } {
170 # Previously kfailed with an exit
171 pass "$test (the program is not being run)"
173 fail "$test (the program is not being run)"
179 # Check that we can step/next our way out of a signal handler.
189 gdb_test "set done = 1" "" "Set done as return will have skipped it"
192 # Check that we can step/next our way into / over a signal handler.
194 # There are at least the following cases: breakpoint @pc VS breakpoint
195 # in handler VS step / next / continue.
197 # Use the real-time itimer, as otherwize the process never gets enough
198 # time to expire the timer.
201 set infinite_loop [gdb_get_line_number {while (!done)}]
202 gdb_test "set itimer = itimer_real"
203 gdb_test "break [gdb_get_line_number {done = 0}]"
205 # Try stepping when there's a signal pending, and a breakpoint at the
206 # handler. Should step into the signal handler.
208 proc skip_to_handler { i } {
211 set prefix "$i to handler"
213 # Run around to the done
214 set test "$prefix; resync"
215 gdb_test_multiple "continue" "$test" {
216 -re "done = 0.*$gdb_prompt " {
219 # other patterns can go here
222 # Advance to the infinite loop
223 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
225 # Make the signal pending
228 # Insert / remove the handler breakpoint.
229 gdb_test "break handler" "" "$prefix; break handler"
230 gdb_test "$i" " handler .*" "$prefix; performing $i"
231 gdb_test "clear handler" "" "$prefix; clear handler"
236 skip_to_handler continue
238 # Try stepping when there's a signal pending, and a breakpoint at the
239 # handler's entry-point. Should step into the signal handler stopping
240 # at the entry-point.
242 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
243 # signal, resume the process at the first instruction of the signal
244 # handler and not the first instruction of the signal trampoline. The
245 # stack is constructed such that the signal handler still appears to
246 # have been called by the trampoline code. This test checks that it
247 # is possible to stop the inferior, even at that first instruction.
249 proc skip_to_handler_entry { i } {
252 set prefix "$i to handler entry"
254 # Run around to the done
255 set test "$prefix; resync"
256 gdb_test_multiple "continue" "$test" {
257 -re "done = 0.*$gdb_prompt " {
260 # other patterns can go here
263 # Advance to the infinite loop
264 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
266 # Make the signal pending
269 # Insert / remove the handler breakpoint.
270 gdb_test "break *handler" "" "$prefix; break handler"
271 gdb_test "$i" " handler .*" "$prefix; performing $i"
272 gdb_test "clear *handler" "" "$prefix; clear handler"
275 skip_to_handler_entry step
276 skip_to_handler_entry next
277 skip_to_handler_entry continue
279 # Try stepping when there's a signal pending but no breakpoints.
280 # Should skip the handler advancing to the next line.
282 proc skip_over_handler { i } {
285 set prefix "$i over handler"
287 # Run around to the done
288 set test "$prefix; resync"
289 gdb_test_multiple "continue" "$test" {
290 -re "done = 0.*$gdb_prompt " {
293 # other patterns can go here
296 # Advance to the infinite loop
297 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
299 # Make the signal pending
302 gdb_test "$i" "done = 0.*" "$prefix; performing $i"
305 skip_over_handler step
306 skip_over_handler next
307 skip_over_handler continue
309 # Try stepping when there's a signal pending, a pre-existing
310 # breakpoint at the current instruction, and a breakpoint in the
311 # handler. Should advance to the signal handler.
313 proc breakpoint_to_handler { i } {
316 set prefix "$i on breakpoint, to handler"
318 # Run around to the done
319 set test "$prefix; resync"
320 gdb_test_multiple "continue" "$test" {
321 -re "done = 0.*$gdb_prompt " {
324 # other patterns can go here
327 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
328 gdb_test "break handler" "" "$prefix; break handler"
330 # Continue to the infinite loop
331 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
333 # Make the signal pending
336 setup_kfail "i*86-*-*" gdb/1738
337 gdb_test "$i" " handler .*" "$prefix; performing $i"
338 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
339 gdb_test "clear handler" "" "$prefix; clear handler"
342 breakpoint_to_handler step
343 breakpoint_to_handler next
344 breakpoint_to_handler continue
346 # Try stepping when there's a signal pending, and a breakpoint at the
347 # handler's entry instruction and a breakpoint at the current
348 # instruction. Should step into the signal handler and breakpoint at
349 # that entry instruction.
351 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
352 # signal, resume the process at the first instruction of the signal
353 # handler and not the first instruction of the signal trampoline. The
354 # stack is constructed such that the signal handler still appears to
355 # have been called by the trampoline code. This test checks that it
356 # is possible to stop the inferior, even at that first instruction.
358 proc breakpoint_to_handler_entry { i } {
361 set prefix "$i on breakpoint, to handler entry"
363 # Run around to the done
364 set test "$prefix; resync"
365 gdb_test_multiple "continue" "$test" {
366 -re "done = 0.*$gdb_prompt " {
369 # other patterns can go here
372 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
373 gdb_test "break *handler" "" "$prefix; break handler"
375 # Continue to the infinite loop
376 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
378 # Make the signal pending
381 setup_kfail "i*86-*-*" gdb/1738
382 gdb_test "$i" " handler .*" "$prefix; performing $i"
383 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
384 gdb_test "clear *handler" "" "$prefix; clear handler"
387 breakpoint_to_handler_entry step
388 breakpoint_to_handler_entry next
389 breakpoint_to_handler_entry continue
391 # Try stepping when there's a signal pending, and a pre-existing
392 # breakpoint at the current instruction, and no breakpoint in the
393 # handler. Should advance to the next line.
395 proc breakpoint_over_handler { i } {
398 set prefix "$i on breakpoint, skip handler"
400 # Run around to the done
401 set test "$prefix; resync"
402 gdb_test_multiple "continue" "$test" {
403 -re "done = 0.*$gdb_prompt " {
406 # other patterns can go here
409 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
411 # Continue to the infinite loop
412 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
414 # Make the signal pending
417 gdb_test "$i" "done = 0.*" "$prefix; performing $i"
418 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
421 breakpoint_over_handler step
422 breakpoint_over_handler next
423 breakpoint_over_handler continue