I noticed an address in a test name:
...
PASS: gdb.base/eh_return.exp: gdb_breakpoint: \
set breakpoint at *0x000000000040071b
...
Stabilize the test name by using "set breakpoint on address" instead.
Likewise in two other test-cases.
Tested on x86_64-linux.
clean_restart ${binfile}
-gdb_breakpoint "*$address" message
+gdb_assert [gdb_breakpoint "*$address" no-message] "set breakpoint on address"
# The assert did not reproduce when running to main, and continuing to the
# breakpoint, so instead, run to the breakpoint.
return -1
}
-gdb_test "b *$next_insn_addr" "Breakpoint .*"
+gdb_test "b *$next_insn_addr" "Breakpoint .*" "set breakpoint on address"
# So that GDB doesn't try to remove the regular breakpoint when the
# step finishes.
# Set the breakpoint by address, and check that GDB reports the
# breakpoint location being the inline function.
- gdb_test "break *$address" ".*Breakpoint .* at $address: file .*$srcfile, line $line."
+ gdb_test "break *$address" \
+ ".*Breakpoint .* at $address: file .*$srcfile, line $line." \
+ "set breakpoint on address"
gdb_test "info break \$bpnum" "in func1 at .*$srcfile:$line"