darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

gdb/testsuite/

Browse source 
* gdb.base/break-entry.exp: Skip if using a stub.
This commit is contained in:
Nathan Froyd 2010-11-12 21:47:47 +00:00
parent ae9d7ce40f
commit b04c2f88b6
2 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View file

@ -1,3 +1,7 @@
2010-11-12 Nathan Froyd <froydnj@codesourcery.com>
* gdb.base/break-entry.exp: Skip if using a stub.
2010-11-12 Nathan Froyd <froydnj@codesourcery.com> 2010-11-12 Nathan Froyd <froydnj@codesourcery.com>
* gdb.python/py-inferior.exp: Pack values in target endianness. * gdb.python/py-inferior.exp: Pack values in target endianness.

14
gdb/testsuite/gdb.base/break-entry.exp
View file

@ -21,6 +21,20 @@ if { [prepare_for_testing ${testfile}.exp ${testfile} start.c {additional_flags=
return -1 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 test "info files"
set entry "" set entry ""
gdb_test_multiple $test $test { gdb_test_multiple $test $test {