[gdb/testsuite] Require use_gdb_stub == 0 where appropriate
authorTom de Vries <tdevries@suse.de>
Wed, 13 Oct 2021 09:06:36 +0000 (11:06 +0200)
committerTom de Vries <tdevries@suse.de>
Wed, 13 Oct 2021 09:06:36 +0000 (11:06 +0200)
commit2786ef85faf16c13029548832c4e4b025bf2624c
treec766139ff53864e476a7d65b537e1339ee3cec63
parent36170420e329a8d6229eb89b38d8680cf39f1d53
[gdb/testsuite] Require use_gdb_stub == 0 where appropriate

When running with target board native-gdbserver, we run into a number of FAILs
due to use of the start command (and similar), which is not supported when
use_gdb_stub == 1.

Fix this by:
- requiring use_gdb_stub == 0 for the entire test-case, or
- guarding some tests in the test-case with use_gdb_stub == 0.

Tested on x86_64-linux.
gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp
gdb/testsuite/gdb.mi/mi-async.exp
gdb/testsuite/gdb.python/python.exp
gdb/testsuite/gdb.reverse/insn-reverse.exp
gdb/testsuite/gdb.tui/tui-missing-src.exp
gdb/testsuite/lib/gdb.exp