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
"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
"done = 1;.*${gdb_prompt} $" {
135 exp_continue
-continue_timer
137 -re
"\} .. handler .*${gdb_prompt} $" {
139 exp_continue
-continue_timer
141 -re
"signal handler called.*${gdb_prompt} $" {
144 -re
"main .*${gdb_prompt} $" {
145 fail
"$test (in main)"
147 -re
"Program exited normally.*${gdb_prompt} $" {
148 fail
"$test (program exited)"
151 -re
"Make handler return now.*y or n. $" {
153 exp_continue
-continue_timer
157 set test
"$prefix; leave signal trampoline"
158 gdb_test_multiple
"$i" "${test}" {
159 -re
"while .*${gdb_prompt} $" {
160 pass
"$test (in main)"
162 -re
"signal handler called.*${gdb_prompt} $" {
164 exp_continue
-continue_timer
166 -re
"return .*${gdb_prompt} $" {
167 fail
"$test (stepped)"
169 -re
"Make .*frame return now.*y or n. $" {
171 exp_continue
-continue_timer
173 -re
"Program exited normally.*${gdb_prompt} $" {
174 kfail gdb
/1639 "$test (program exited)"
177 -re
"The program is not being run.*${gdb_prompt} $" {
178 if { $program_exited
} {
179 # Previously kfailed with an exit
180 pass
"$test (the program is not being run)"
182 fail
"$test (the program is not being run)"
188 # Check that we can step
/next our way out of a
signal handler.
198 gdb_test
"set done = 1" "" "Set done as return will have skipped it"
201 # Check that we can step
/next our way into
/ over a
signal handler.
203 # There are at least the following cases
: breakpoint @pc VS breakpoint
204 # in handler VS step
/ next
/ continue.
206 # Use the real
-time itimer
, as otherwize the process never gets enough
207 # time to expire the timer.
210 set infinite_loop
[gdb_get_line_number
{while (!done
)}]
211 gdb_test
"set itimer = itimer_real"
212 gdb_test
"break [gdb_get_line_number {done = 0}]"
214 # Try stepping when there
's a signal pending, and a breakpoint at the
215 # handler. Should step into the signal handler.
217 proc skip_to_handler { i } {
220 set prefix "$i to handler"
222 # Run around to the done
223 # You can add more patterns to this if you need them.
224 set test "$prefix; resync"
225 gdb_test_multiple "continue" "$test" {
226 -re "done = 0.*$gdb_prompt " {
231 # Advance to the infinite loop
232 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
234 # Make the signal pending
237 # Insert / remove the handler breakpoint.
238 gdb_test "break handler" "" "$prefix; break handler"
239 gdb_test "$i" " handler .*" "$prefix; performing $i"
240 gdb_test "clear handler" "" "$prefix; clear handler"
245 skip_to_handler continue
247 # Try stepping when there's a
signal pending
, and a breakpoint at the
248 # handler
's entry-point. Should step into the signal handler stopping
249 # at the entry-point.
251 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
252 # signal, resume the process at the first instruction of the signal
253 # handler and not the first instruction of the signal trampoline. The
254 # stack is constructed such that the signal handler still appears to
255 # have been called by the trampoline code. This test checks that it
256 # is possible to stop the inferior, even at that first instruction.
258 proc skip_to_handler_entry { i } {
261 set prefix "$i to handler entry"
263 # Run around to the done
264 # You can add more patterns to this if you need them.
265 set test "$prefix; resync"
266 gdb_test_multiple "continue" "$test" {
267 -re "done = 0.*$gdb_prompt " {
272 # Advance to the infinite loop
273 gdb_test "advance $infinite_loop" "" "$prefix; advance to infinite loop"
275 # Make the signal pending
278 # Insert / remove the handler breakpoint.
279 gdb_test "break *handler" "" "$prefix; break handler"
280 gdb_test "$i" " handler .*" "$prefix; performing $i"
281 gdb_test "clear *handler" "" "$prefix; clear handler"
284 skip_to_handler_entry step
285 skip_to_handler_entry next
286 skip_to_handler_entry continue
288 # Try stepping when there's a
signal pending but no breakpoints.
289 # Should skip the handler advancing to the next line.
291 proc skip_over_handler
{ i
} {
294 set prefix
"$i over handler"
296 # Run around to the done
297 # You can add more patterns to this
if you need them.
298 set test
"$prefix; resync"
299 gdb_test_multiple
"continue" "$test" {
300 -re
"done = 0.*$gdb_prompt " {
305 # Advance to the infinite loop
306 gdb_test
"advance $infinite_loop" "" "$prefix; advance to infinite loop"
308 # Make the
signal pending
311 gdb_test
"$i" "done = 0.*" "$prefix; performing $i"
314 skip_over_handler step
315 skip_over_handler next
316 skip_over_handler
continue
318 # Try stepping when there
's a signal pending, a pre-existing
319 # breakpoint at the current instruction, and a breakpoint in the
320 # handler. Should advance to the signal handler.
322 proc breakpoint_to_handler { i } {
325 set prefix "$i on breakpoint, to handler"
327 # Run around to the done
328 # You can add more patterns to this if you need them.
329 set test "$prefix; resync"
330 gdb_test_multiple "continue" "$test" {
331 -re "done = 0.*$gdb_prompt " {
336 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
337 gdb_test "break handler" "" "$prefix; break handler"
339 # Continue to the infinite loop
340 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
342 # Make the signal pending
345 setup_kfail "i*86-*-*" gdb/1738
346 gdb_test "$i" " handler .*" "$prefix; performing $i"
347 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
348 gdb_test "clear handler" "" "$prefix; clear handler"
351 breakpoint_to_handler step
352 breakpoint_to_handler next
353 breakpoint_to_handler continue
355 # Try stepping when there's a
signal pending
, and a breakpoint at the
356 # handler
's entry instruction and a breakpoint at the current
357 # instruction. Should step into the signal handler and breakpoint at
358 # that entry instruction.
360 # Some systems (e.x., GNU/Linux as of 2004-08-30), when delivering a
361 # signal, resume the process at the first instruction of the signal
362 # handler and not the first instruction of the signal trampoline. The
363 # stack is constructed such that the signal handler still appears to
364 # have been called by the trampoline code. This test checks that it
365 # is possible to stop the inferior, even at that first instruction.
367 proc breakpoint_to_handler_entry { i } {
370 set prefix "$i on breakpoint, to handler entry"
372 # Run around to the done
373 # You can add more patterns to this if you need them.
374 set test "$prefix; resync"
375 gdb_test_multiple "continue" "$test" {
376 -re "done = 0.*$gdb_prompt " {
381 gdb_test "break $infinite_loop" "" "$prefix; break infinite loop"
382 gdb_test "break *handler" "" "$prefix; break handler"
384 # Continue to the infinite loop
385 gdb_test "continue" "while ..done.*" "$prefix; continue to infinite loop"
387 # Make the signal pending
390 setup_kfail "i*86-*-*" gdb/1738
391 gdb_test "$i" " handler .*" "$prefix; performing $i"
392 gdb_test "clear $infinite_loop" "" "$prefix; clear infinite loop"
393 gdb_test "clear *handler" "" "$prefix; clear handler"
396 breakpoint_to_handler_entry step
397 breakpoint_to_handler_entry next
398 breakpoint_to_handler_entry continue
400 # Try stepping when there's a
signal pending
, and a pre
-existing
401 # breakpoint at the current instruction
, and no breakpoint in the
402 # handler. Should advance to the next line.
404 proc breakpoint_over_handler
{ i
} {
407 set prefix
"$i on breakpoint, skip handler"
409 # Run around to the done
410 # You can add more patterns to this
if you need them.
411 set test
"$prefix; resync"
412 gdb_test_multiple
"continue" "$test" {
413 -re
"done = 0.*$gdb_prompt " {
418 gdb_test
"break $infinite_loop" "" "$prefix; break infinite loop"
420 #
Continue to the infinite loop
421 gdb_test
"continue" "while ..done.*" "$prefix; continue to infinite loop"
423 # Make the
signal pending
426 gdb_test
"$i" "done = 0.*" "$prefix; performing $i"
427 gdb_test
"clear $infinite_loop" "" "$prefix; clear infinite loop"
430 breakpoint_over_handler step
431 breakpoint_over_handler next
432 breakpoint_over_handler
continue