Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathan Froyd <froydnj@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] skip break-entry.exp when using a stub
Date: Fri, 29 Oct 2010 19:20:00 -0000	[thread overview]
Message-ID: <1288380040-22077-1-git-send-email-froydnj@codesourcery.com> (raw)

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


             reply	other threads:[~2010-10-29 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 19:20 Nathan Froyd [this message]
2010-10-29 20:10 ` Pedro Alves
2010-11-02 17:58 ` Joel Brobecker
2010-11-02 18:04   ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1288380040-22077-1-git-send-email-froydnj@codesourcery.com \
    --to=froydnj@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox