From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Nathan Froyd <froydnj@codesourcery.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Question re: testsuite, "isnative", "is_remote" etc.
Date: Thu, 13 Jan 2011 19:54:00 -0000 [thread overview]
Message-ID: <4D2F5881.4020703@vmware.com> (raw)
In-Reply-To: <20110113193211.GO2518@adacore.com>
Joel Brobecker wrote:
>>> I used [target_info exists use_gdb_stub] last time I fixed a test like
>>> this (gdb.base/break-entry.exp).
>>
>> Yep, I've been tempted to use that too. But I think "use_gdb_stub"
>> is still something different. It was meant to refer to those old
>> stubs like i386-stub.c, not to gdbserver. There used to be some
>> magic that you had to do, like this in break.c:
>
> I looked at the documented procedure for testing with gdbserver,
> and everything is setup by the boards file. So, it's basically
> a question of convention.
>
> The boards file in the wiki do the following:
>
> set_board_info use_gdb_stub 1
>
> So that might be the best solution, even if we might be abusing
> its original intent.
>
Then what is the corresponding test for the testsuite?
And do we need to revise some of the existing tests?
next prev parent reply other threads:[~2011-01-13 19:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 23:14 Michael Snyder
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 [this message]
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=4D2F5881.4020703@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.com \
--cc=froydnj@codesourcery.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