This is the mail archive of the
mailing list for the GDB project.
Re: Question re: testsuite, "isnative", "is_remote" etc.
- From: Michael Snyder <msnyder at vmware dot com>
- To: Kevin Pouget <kevin dot pouget at gmail dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Thu, 13 Jan 2011 10:27:23 -0800
- Subject: Re: Question re: testsuite, "isnative", "is_remote" etc.
- References: <4D2E35C5.firstname.lastname@example.org> <20110112232003.GK2518@adacore.com> <4D2E37FB.email@example.com> <AANLkTi=R-L9-=O6cWW_aTBAoZFmmo_MMB57g2HZy85je@mail.gmail.com>
Kevin Pouget wrote:
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.