diff options
| author | Tom de Vries <tdevries@suse.de> | 2021-10-13 11:06:36 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2021-10-13 11:06:36 +0200 |
| commit | 2786ef85faf16c13029548832c4e4b025bf2624c (patch) | |
| tree | c766139ff53864e476a7d65b537e1339ee3cec63 /gdb/testsuite/gdb.reverse/insn-reverse.exp | |
| parent | 36170420e329a8d6229eb89b38d8680cf39f1d53 (diff) | |
| download | gdb-2786ef85faf16c13029548832c4e4b025bf2624c.zip gdb-2786ef85faf16c13029548832c4e4b025bf2624c.tar.gz gdb-2786ef85faf16c13029548832c4e4b025bf2624c.tar.bz2 | |
[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.
Diffstat (limited to 'gdb/testsuite/gdb.reverse/insn-reverse.exp')
| -rw-r--r-- | gdb/testsuite/gdb.reverse/insn-reverse.exp | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.reverse/insn-reverse.exp b/gdb/testsuite/gdb.reverse/insn-reverse.exp index 47f0166..50b8e9c 100644 --- a/gdb/testsuite/gdb.reverse/insn-reverse.exp +++ b/gdb/testsuite/gdb.reverse/insn-reverse.exp @@ -17,6 +17,9 @@ if ![supports_reverse] { return } +# Check if start command is supported. +require use_gdb_stub 0 + standard_testfile if {[prepare_for_testing "failed to prepare" $testfile $srcfile \ |