FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

For IA-64, allow ``finish'' to land on caller rather than on next executable

Browse source 
line after the caller.
This commit is contained in:
Kevin Buettner 2000-05-13 01:38:05 +00:00
parent bf9198f149
commit 8216cda9b4
2 changed files with 15 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
gdb/testsuite/ChangeLog
View file

@ -1,3 +1,10 @@
2000-05-12 Kevin Buettner <kevinb@redhat.com>
* gdb.base/step-test.exp: On IA-64 targets, when stepping out of
a call, do not require that gdb stop on the line after the call.
Instead, it is permissible for gdb to stop on the line of the
call itself.
2000-05-08 Michael Snyder <msnyder@seadog.cygnus.com> 2000-05-08 Michael Snyder <msnyder@seadog.cygnus.com>
* gdb.base/interrupt.exp: Make "pass" message say "send" * gdb.base/interrupt.exp: Make "pass" message say "send"

12
gdb/testsuite/gdb.base/step-test.exp
View file

@ -75,8 +75,10 @@ gdb_test "step" ".*${decimal}.*myglob.*" "step into"
# instruction, which is attributed to the line containing the function # instruction, which is attributed to the line containing the function
# call? # call?
# On PA64 we end up at a different instruction than PA32 # On PA64, we end up at a different instruction than PA32.
if { [istarget "hppa2.0w-hp-hpux*"] } { # On IA-64, we also end up on callee instead of on the next line due
# to the restoration of the global pointer (which is a caller-save).
if { [istarget "hppa2.0w-hp-hpux*"] || [istarget "ia64-*-*"]} {
send_gdb "finish\n" send_gdb "finish\n"
gdb_expect { gdb_expect {
-re ".*${decimal}.*a.*5.*= a.*3.*$gdb_prompt $" { pass "step out 1" } -re ".*${decimal}.*a.*5.*= a.*3.*$gdb_prompt $" { pass "step out 1" }
@ -171,8 +173,10 @@ gdb_expect {
pass "stepi: finish call" pass "stepi: finish call"
} }
-re ".*${decimal}.*callee.*STEPI.*$gdb_prompt $" { -re ".*${decimal}.*callee.*STEPI.*$gdb_prompt $" {
# On PA64 we end up at a different instruction than PA32 # On PA64, we end up at a different instruction than PA32.
if { [istarget "hppa2.0w-hp-hpux*"] } { # On IA-64, we end up on callee instead of on the following line due
# to the restoration of the global pointer.
if { [istarget "hppa2.0w-hp-hpux*"] || [istarget "ia64-*-*"] } {
pass "stepi: finish call 2" pass "stepi: finish call 2"
} else { } else {
fail "stepi: finish call 2" fail "stepi: finish call 2"