From: Michael Snyder <msnyder@vmware.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Question re: testsuite, "isnative", "is_remote" etc.
Date: Thu, 13 Jan 2011 18:27:00 -0000 [thread overview]
Message-ID: <4D2F440B.6020001@vmware.com> (raw)
In-Reply-To: <AANLkTi=R-L9-=O6cWW_aTBAoZFmmo_MMB57g2HZy85je@mail.gmail.com>
Kevin Pouget wrote:
> hello,
>
> 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.
>
> just the point of view of a 'gdb beginner', but why don't you rely a bit more on the target abstraction?
> maybe adding a "to_is_remote_target" in the 'struct target_ops' is too complicated,
>
> but what about testing if the 'remote' target has been pushed on the current target stack?
That would give me exactly the result that I want.
Unfortunately, this test (is-remote) is done outside of gdb, in the
dejagnu test suite, and is often done before gdb even starts. So that
information is not available.
next prev parent reply other threads:[~2011-01-13 18:27 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 [this message]
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=4D2F440B.6020001@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=kevin.pouget@gmail.com \
/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