Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fred Fish <fnf@specifix.com>
To: gdb-patches@sourceware.org
Cc: fnf@specifix.com
Subject: [RFA] Don't try to run auxv tests in simulator
Date: Thu, 11 May 2006 09:44:00 -0000	[thread overview]
Message-ID: <200605110545.35426.fnf@specifix.com> (raw)

AFAIK all available simulators don't support auxv info, so trying to
run the auxv tests will fail.  They also need corefile support.

I see that corefile.exp has:

  # are we on a target board
  if ![isnative] then {
      return
  }

which may be too restrictive for auxv.  So I'd propose suppressing the
auxv tests just for simulators, for now at least.

2006-05-11  Fred Fish  <fnf@specifix.com>

	* gdb.base/auxv.exp: Simulators don't support auxv info
	so don't run test if executing in a simulator.

Index: gdb.base/auxv.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/auxv.exp,v
retrieving revision 1.4
diff -u -p -r1.4 auxv.exp
--- gdb.base/auxv.exp	2 May 2005 20:57:30 -0000	1.4
+++ gdb.base/auxv.exp	11 May 2006 09:43:40 -0000
@@ -30,6 +30,12 @@ if $tracelevel then {
 set prms_id 0
 set bug_id 0
 
+# Simulators don't support auxv.
+if [target_info exists is_simulator] {
+    unsupported "auxv tests running in simulator"
+    return
+}
+
 set testfile "auxv"
 set srcfile ${testfile}.c
 set binfile ${objdir}/${subdir}/${testfile}



             reply	other threads:[~2006-05-11  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11  9:44 Fred Fish [this message]
2006-05-11 12:41 ` Daniel Jacobowitz
2006-05-11 13:13   ` Fred Fish
2006-05-11 13:08     ` Daniel Jacobowitz
2006-05-11 17:38   ` Nathan J. Williams
2006-05-12 20:48   ` Mark Kettenis

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=200605110545.35426.fnf@specifix.com \
    --to=fnf@specifix.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