Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Question re: testsuite, "isnative", "is_remote" etc.
Date: Wed, 12 Jan 2011 23:14:00 -0000	[thread overview]
Message-ID: <4D2E35C5.60206@vmware.com> (raw)

What's the recommended way of skipping a test case if it shouldn't run 
remotely?

I see a lot of tests that use "if not isnative", but that surely isn't 
right, since that test only compares the host and target board names.

Then there is a test called is_remote, but that mostly does the same 
thing, except it also tests a board variable called "isremote", which is 
only true if you happen to remember to set it in your board file.

I'm thinking that there should be some test that checks for
"use_gdb_stub" or "gdb_protocol".  But of course you have to set those 
in your board file too.

What's the right answer?   ;-/


             reply	other threads:[~2011-01-12 23:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 23:14 Michael Snyder [this message]
2011-01-12 23:19 ` Joel Brobecker
2011-01-12 23:20 ` Joel Brobecker
2011-01-12 23:23   ` Michael Snyder
     [not found]     ` <AANLkTi=R-L9-=O6cWW_aTBAoZFmmo_MMB57g2HZy85je@mail.gmail.com>
2011-01-13 18:27       ` Michael Snyder
2011-01-13 18:37         ` Joel Brobecker
2011-01-13 18:51           ` Michael Snyder
2011-01-13 18:40 ` Nathan Froyd
2011-01-13 19:04   ` Michael Snyder
2011-01-13 19:32     ` Joel Brobecker
2011-01-13 19:54       ` Michael Snyder
2011-01-13 20:53         ` Joel Brobecker
2011-01-13 20:59           ` Michael Snyder
2011-01-13 21:00             ` Nathan Froyd
2011-01-14  1:26               ` Michael Snyder
2011-01-13 21:27             ` Joel Brobecker
2011-01-13 21:29               ` Joel Brobecker

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=4D2E35C5.60206@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb@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