diff options
author | Tom de Vries <tdevries@suse.de> | 2022-05-11 09:32:58 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-05-11 09:32:58 +0200 |
commit | e21d8399303b3d2b77e1a526dcbeffcfce678e6f (patch) | |
tree | 790c1e8f1a0d3cc03ef5db21a1fd434b715f3976 /ld/testplug3.c | |
parent | d423425393e4ef27cabdda4134ae27905a18fcf7 (diff) | |
download | gdb-e21d8399303b3d2b77e1a526dcbeffcfce678e6f.zip gdb-e21d8399303b3d2b77e1a526dcbeffcfce678e6f.tar.gz gdb-e21d8399303b3d2b77e1a526dcbeffcfce678e6f.tar.bz2 |
[gdb/testsuite] Remove target limits in gdb.base/catch-syscall.exp
In test-case gdb.base/catch-syscall.exp, proc test_catch_syscall_multi_arch we
test for supported targets using istarget, like so:
...
if { [istarget "i*86-*-*"] || [istarget "x86_64-*-*"] } {
...
} elseif { [istarget "powerpc-*-linux*"] \
|| [istarget "powerpc64*-linux*"] } {
...
...
but the tests excercised there can all be executed if gdb is configured with
--enable-targets=all.
Rewrite the proc to iterate over all cases, and check if the test is supported
by trying "set arch $arch1" and "set arch $arch2".
Tested on x86_64-linux, with:
- a gdb build with --enable-targets=all, and
- a gdb build build with my usual --enable-targets setting (too long to
include here) which means the sparc vs sparc:v9 case is unsupported.
Diffstat (limited to 'ld/testplug3.c')
0 files changed, 0 insertions, 0 deletions