aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.arch/pa-nullify.exp
diff options
context:
space:
mode:
Diffstat (limited to 'gdb/testsuite/gdb.arch/pa-nullify.exp')
-rw-r--r--gdb/testsuite/gdb.arch/pa-nullify.exp13
1 files changed, 7 insertions, 6 deletions
diff --git a/gdb/testsuite/gdb.arch/pa-nullify.exp b/gdb/testsuite/gdb.arch/pa-nullify.exp
index 87afe7a..cb8eeeb 100644
--- a/gdb/testsuite/gdb.arch/pa-nullify.exp
+++ b/gdb/testsuite/gdb.arch/pa-nullify.exp
@@ -40,9 +40,10 @@ if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {}] !
return -1
}
-clean_restart $binfile
+clean_restart
+gdb_load $binfile
-# In the first test, we do a "step" on a function whose last instruction
+# In the first test, we do a "step" on a function whose last instruction
# contains a branch-with-nullify. The instruction in the delay slot belongs
# to the next function. We verify that when we step off the first function
# that we end up back at the caller and not at the second instruction.
@@ -64,9 +65,9 @@ gdb_test_multiple "stepi" "${test}" {
}
}
-# In the second test, we verify that we can get a proper backtrace
+# In the second test, we verify that we can get a proper backtrace
# even when we are in a nullified instruction that belongs to the next function.
-# We also verify that when stepping over a branch-with-nullify insn that we
+# We also verify that when stepping over a branch-with-nullify insn that we
# stay on the same insn for two steps.
proc get_addr_of_sym { sym } {
@@ -126,7 +127,7 @@ if {![runto_main]} {
}
gdb_breakpoint "*$foo_last"
gdb_test "continue" "Breakpoint \[0-9\]*,.* in foo.*" "$test: continue to breakpoint"
-if [gen_core $test] {
+if {[gen_core $test]} {
test_core_bt $test
}
@@ -137,6 +138,6 @@ if {![runto_main]} {
gdb_breakpoint "*$foo_last"
gdb_test "continue" "Breakpoint \[0-9\]*,.* in foo.*" "$test: continue to breakpoint"
gdb_test "stepi" ".*in foo.*" "$test: step to nullified instruction"
-if [gen_core $test] {
+if {[gen_core $test]} {
test_core_bt $test
}