This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PATCH] skip break-entry.exp when using a stub
- From: Nathan Froyd <froydnj at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Fri, 29 Oct 2010 12:20:40 -0700
- Subject: [PATCH] skip break-entry.exp when using a stub
This patch skips gdb.base/break-entry.exp when using a stub.
prepare_for_testing already stopped the program at its entry, so the
test will not work correctly.
Tested with cross to powerpc-linux-gnu using gdbserver. OK to commit?
-Nathan
* gdb.base/break-entry.exp: Skip if using a stub.
---
gdb/testsuite/gdb.base/break-entry.exp | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/gdb/testsuite/gdb.base/break-entry.exp b/gdb/testsuite/gdb.base/break-entry.exp
index d4b86a3..4e4515b 100644
--- a/gdb/testsuite/gdb.base/break-entry.exp
+++ b/gdb/testsuite/gdb.base/break-entry.exp
@@ -21,6 +21,15 @@ if { [prepare_for_testing ${testfile}.exp ${testfile} start.c {additional_flags=
return -1
}
+# If we're using a stub, we'll already be stopped at the entry point
+# when we connect. Don't bother trying to work around this in the
+# testing below.
+
+if [target_info exists use_gdb_stub] {
+ untested ${testfile}.exp
+ return
+}
+
set test "info files"
set entry ""
gdb_test_multiple $test $test {
--
1.6.3.2