This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/2] GDB test suite: Add helper for locating core files
On Fri, Oct 13 2017, Maciej W. Rozycki wrote:
> On Thu, 12 Oct 2017, Andreas Arnez wrote:
>
>> > This seems incorrect to me. "isnative" only checks
>> > if the build and target _triplets_ are the same. So
>> > foo-linux-gnu gdb x foo-linux-gnu gdbserver on separate
>> > machine still returns isnative==true.
>>
>> Exactly, that's why I originally wrote is_remote instead. And I also
>> wondered why the core dump tests check isnative. Does anyone run the
>> testsuite on a native remote setup?
>
> Well, I had cases where I did that, and offhand I can find two reasons:
>
> 1. You want to verify `gdbserver' itself rather than GDB, in which case
> you may even run it locally (i.e. where the remote target is really
> `localhost').
This is the native-gdbserver setup, right? In that case the core dump
tests should work...
> 2. You want to test a feature (e.g. an extra register set) only your
> target system has and it is too slow or unequipped to run DejaGNU
> itself.
...and in this case they shouldn't. Do you remember whether you saw
FAILs from corefile.exp and friends?
--
Andreas