| commit | b0af93ad2ba7db505e5967aeebe37f88b17e44cf | |
| author | Tom de Vries <tdevries@suse.de> | |
| Mon, 27 Mar 2023 15:40:06 +0000 (27 17:40 +0200) | ||
| committer | Tom de Vries <tdevries@suse.de> | |
| Mon, 27 Mar 2023 15:40:06 +0000 (27 17:40 +0200) | ||
| tree | b877eb2e5efee114eb380ee783fde48696280f71 | treesnapshot (tar.gz zip) |
| parent | 72a8f763233c11052b8b7eee5d2d8fb23e118c97 | commitdiff |
[gdb/testsuite] Skip do_self_tests on remote host
In do_self_tests we try to find out the location of the gdb to debug, which
will then be copied and renamed to xgdb.
In principle, the host board specifies the location of GDB, on host.
With remote host, we could upload that gdb from host to build/target, but we
would miss the data directory (which is listed as the reason to skip
do_self_tests for remote target).
We could fix that by instead taking the gdb from build instead, but that
wouldn't work with installed testing.
It seems easier to just skip this on remote host.
It could be made to work for the "[is_remote host] && [is_remote target]
&& host == target" scenario (see board local-remote-host-native.exp), but
that doesn't seem worth the effort.
Tested on x86_64-linux.
In do_self_tests we try to find out the location of the gdb to debug, which
will then be copied and renamed to xgdb.
In principle, the host board specifies the location of GDB, on host.
With remote host, we could upload that gdb from host to build/target, but we
would miss the data directory (which is listed as the reason to skip
do_self_tests for remote target).
We could fix that by instead taking the gdb from build instead, but that
wouldn't work with installed testing.
It seems easier to just skip this on remote host.
It could be made to work for the "[is_remote host] && [is_remote target]
&& host == target" scenario (see board local-remote-host-native.exp), but
that doesn't seem worth the effort.
Tested on x86_64-linux.
| gdb/testsuite/lib/selftest-support.exp | diffblobblamehistory |