Eliminate is_remote check in gdb.base/shlib-call.exp

gdb/testsuite/ChangeLog:
2017-10-13  Pedro Alves  <palves@redhat.com>

	* gdb.base/shlib-call.exp (top level): Use gdb_run_cmd and remove
	is_remote target check.
This commit is contained in:
Pedro Alves 2017-10-13 10:11:57 +01:00
parent c2508e905f
commit 5e830d9807
2 changed files with 22 additions and 13 deletions

View File

@ -1,3 +1,8 @@
2017-10-13 Pedro Alves <palves@redhat.com>
* gdb.base/shlib-call.exp (top level): Use gdb_run_cmd and remove
is_remote target check.
2017-10-13 Pedro Alves <palves@redhat.com>
* gdb.base/scope.exp: Use build_executable + clean_restart +

View File

@ -170,18 +170,22 @@ gdb_test_no_output "set width 0"
# test that we can re-set breakpoints in shared libraries
gdb_breakpoint "shr1" "allow-pending"
# FIXME: should not send "run" explicitly. Non-portable.
if ![is_remote target] {
gdb_test "run" "Starting program:.*Breakpoint .,.*" \
"run to bp in shared library"
gdb_continue_to_end "" continue 1
gdb_test "run" "Starting program:.*Breakpoint .,.*" \
"re-run to bp in shared library (PR's 16495, 18213)"
gdb_continue_to_end "" continue 1
set test "run to bp in shared library"
gdb_run_cmd
gdb_test_multiple "" $test {
-re "Breakpoint .,.*${gdb_prompt} " {
pass $test
}
}
return 0
gdb_continue_to_end "" continue 1
set test "re-run to bp in shared library (PR's 16495, 18213)"
gdb_run_cmd
gdb_test_multiple "" $test {
-re "Breakpoint .,.*${gdb_prompt} " {
pass $test
}
}
gdb_continue_to_end "" continue 1