| commit | b91f16040a6a531e010fc4e798f03159832fdd6a | |
| author | Tom de Vries <tdevries@suse.de> | |
| Mon, 13 Mar 2023 16:20:09 +0000 (13 17:20 +0100) | ||
| committer | Tom de Vries <tdevries@suse.de> | |
| Mon, 13 Mar 2023 16:20:09 +0000 (13 17:20 +0100) | ||
| tree | 993206bbfff2352cd5c96acbdafa8a8e2c28bc21 | treesnapshot (tar.gz zip) |
| parent | 72f160d012233b7a322cd626e11f787f501beee2 | commitdiff |
[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.
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.
| gdb/testsuite/gdb.tui/tui-nl-filtered-output.exp | diffblobblamehistory |