diff options
| author | Tom de Vries <tdevries@suse.de> | 2023-03-13 17:20:09 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2023-03-13 17:20:09 +0100 |
| commit | b91f16040a6a531e010fc4e798f03159832fdd6a (patch) | |
| tree | 993206bbfff2352cd5c96acbdafa8a8e2c28bc21 | |
| parent | 72f160d012233b7a322cd626e11f787f501beee2 (diff) | |
| download | binutils-b91f16040a6a531e010fc4e798f03159832fdd6a.zip binutils-b91f16040a6a531e010fc4e798f03159832fdd6a.tar.gz binutils-b91f16040a6a531e010fc4e798f03159832fdd6a.tar.bz2 | |
[gdb/testsuite] Fix gdb.tui/tui-nl-filtered-output.exp for remote host
When running test-case gdb.tui/tui-nl-filtered-output.exp with host board
local-remote-host-notty and target board native-gdbserver, I get:
...
FAIL: gdb.tui/tui-nl-filtered-output.exp: check printf output
...
The problem is that Term::enter_tui is returning 0, but the test-case doesn't
check for this, and consequently runs unsupported tests.
Fix this by adding the missing check.
Tested on x86_64-linux.
| -rw-r--r-- | gdb/testsuite/gdb.tui/tui-nl-filtered-output.exp | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.tui/tui-nl-filtered-output.exp b/gdb/testsuite/gdb.tui/tui-nl-filtered-output.exp index 5b1d6b7..8f85ae7 100644 --- a/gdb/testsuite/gdb.tui/tui-nl-filtered-output.exp +++ b/gdb/testsuite/gdb.tui/tui-nl-filtered-output.exp @@ -36,7 +36,10 @@ tuiterm_env # Setup and enter TUI mode. Term::clean_restart 24 80 -Term::enter_tui +if {![Term::enter_tui]} { + unsupported "TUI not supported" + return +} # Send the command, and check the output is correctly split over # multiple lines. |