Re: [PATCH] Skipping tests that use remote protocol

[Yao Qi <yao at codesourcery dot com>]

Don Breazeal <donb@codesourcery.com> writes:

> Other procedures are also used that don't really check the right thing.
>
> * isnative checks the build triplet against the target triplet.
>
> * gdb_is_target_remote and target_is_gdbserver don't differentiate between
>   remote and extended-remote.  Both require GDB to be running, which makes
>   using them to skip a test less efficient than a procedure that uses info
>   from the target board config file.
>
> * target_info use_gdb_stub is used in lib/gdb.exp to explicitly determine
>   if a target is remote and not extended-remote.
>
> If we reach consensus on this approach I'll follow up with patches to
> convert other tests to use these procedures instead of is_remote,
> isnative, and so on.

Does "![isnative] || [is_remote host] || [target_info exists use_gdb_stub]"
work for you?  It is used in some attach related tests.

-- 
Yao (éå)