From b04c2f88b6a0bcb3c241c6a2f91d93bd3476bbf2 Mon Sep 17 00:00:00 2001 From: Nathan Froyd Date: Fri, 12 Nov 2010 21:47:47 +0000 Subject: [PATCH] gdb/testsuite/ * gdb.base/break-entry.exp: Skip if using a stub. --- gdb/testsuite/ChangeLog | 4 ++++ gdb/testsuite/gdb.base/break-entry.exp | 14 ++++++++++++++ 2 files changed, 18 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 0694d9c4819..2a6c11bd274 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,7 @@ +2010-11-12 Nathan Froyd + + * gdb.base/break-entry.exp: Skip if using a stub. + 2010-11-12 Nathan Froyd * gdb.python/py-inferior.exp: Pack values in target endianness. diff --git a/gdb/testsuite/gdb.base/break-entry.exp b/gdb/testsuite/gdb.base/break-entry.exp index 13605042e6e..151eb046348 100644 --- a/gdb/testsuite/gdb.base/break-entry.exp +++ b/gdb/testsuite/gdb.base/break-entry.exp @@ -21,6 +21,20 @@ if { [prepare_for_testing ${testfile}.exp ${testfile} start.c {additional_flags= return -1 } +# If we're using a stub, we'll already be debugging a live program and +# stopped at the entry point when we connect, and so the runto below +# will issue a "continue", which always skips any breakpoint at PC. +# When testing with a native target (or some other target that supports +# "run"), runto will do a "run", which first creates the process, +# leaving the PC at the entry point, just like the stub case, but then +# continues the process with the equivalent of "jump *$PC", which +# triggers any breakpoint at $PC. The latter is what we want to test. + +if [target_info exists use_gdb_stub] { + untested ${testfile}.exp + return +} + set test "info files" set entry "" gdb_test_multiple $test $test { -- 2.30.2