summaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2021-10-13 11:06:36 +0200
committerTom de Vries <tdevries@suse.de>2021-10-13 11:06:36 +0200
commit2786ef85faf16c13029548832c4e4b025bf2624c (patch)
treec766139ff53864e476a7d65b537e1339ee3cec63 /gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp
parent36170420e329a8d6229eb89b38d8680cf39f1d53 (diff)
downloadbinutils-gdb-2786ef85faf16c13029548832c4e4b025bf2624c.tar.gz
[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.dwarf2/frame-inlined-in-outer-frame.exp')
-rw-r--r--gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp b/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp
index f95558dffef..e19c474bb60 100644
--- a/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp
+++ b/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp
@@ -25,6 +25,9 @@
# Because of (1), the test has to be written in assembly with explicit CFI
# directives.
+# Check if starti command is supported.
+require use_gdb_stub 0
+
load_lib dwarf.exp
if {![dwarf2_support]} {