aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2023-03-13 17:20:09 +0100
committerTom de Vries <tdevries@suse.de>2023-03-13 17:20:09 +0100
commite1b8f529d3246b031352882c3eb85fa2ccedd02e (patch)
tree78c6feb13aa4ae0fc4361d81de0c5ab484d61b66
parentb91f16040a6a531e010fc4e798f03159832fdd6a (diff)
downloadgdb-e1b8f529d3246b031352882c3eb85fa2ccedd02e.zip
gdb-e1b8f529d3246b031352882c3eb85fa2ccedd02e.tar.gz
gdb-e1b8f529d3246b031352882c3eb85fa2ccedd02e.tar.bz2
[gdb/testsuite] Fix gdb.tui/tui-layout.exp for remote host
When running test-case gdb.tui/tui-layout.exp with host board local-remote-host-notty and target board native-gdbserver, I get: ... FAIL: gdb.tui/tui-layout.exp: terminal=dumb: execution=false: layout=asm: \ layout asm (timeout) ... The problem is that the test-case expects that the default "setenv TERM dumb" has effect, which is not the case for remote host. Fix this by skipping the test for remote host. Tested on x86_64-linux.
-rw-r--r--gdb/testsuite/gdb.tui/tui-layout.exp4
1 files changed, 4 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.tui/tui-layout.exp b/gdb/testsuite/gdb.tui/tui-layout.exp
index c7fdb1b..1382338 100644
--- a/gdb/testsuite/gdb.tui/tui-layout.exp
+++ b/gdb/testsuite/gdb.tui/tui-layout.exp
@@ -61,6 +61,10 @@ proc test_layout_or_focus {layout_name terminal execution} {
}
if {$dumb_terminal} {
+ if { [is_remote host] } {
+ # setenv TERM dummy has no effect on remote host.
+ return
+ }
gdb_test "layout $layout_name" \
"Cannot enable the TUI: terminal doesn't support cursor addressing \\\[TERM=dumb\\\]"
} else {