aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/lib
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 /gdb/python/lib
parentb91f16040a6a531e010fc4e798f03159832fdd6a (diff)
downloadbinutils-e1b8f529d3246b031352882c3eb85fa2ccedd02e.zip
binutils-e1b8f529d3246b031352882c3eb85fa2ccedd02e.tar.gz
binutils-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.
Diffstat (limited to 'gdb/python/lib')
0 files changed, 0 insertions, 0 deletions