diff options
author | Bernd Edlinger <bernd.edlinger@hotmail.de> | 2024-08-12 17:32:44 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2024-08-12 17:32:44 +0200 |
commit | 250f1bbaf33e25da8b6beaf2e0e8a46c46127b1b (patch) | |
tree | 5352e63ed8fc5e73e7805aba90e3e4db74f6e21b /gdb/python | |
parent | 37ef6d976a777f186568f2b629f04a6bd9706ed7 (diff) | |
download | binutils-250f1bbaf33e25da8b6beaf2e0e8a46c46127b1b.zip binutils-250f1bbaf33e25da8b6beaf2e0e8a46c46127b1b.tar.gz binutils-250f1bbaf33e25da8b6beaf2e0e8a46c46127b1b.tar.bz2 |
[gdb/testsuite] Fix gdb.tui/wrap-line.exp with wrapping disabled
There are a couple of ways that readline wrapping can be disabled:
- using "set horizontal-scroll-mode on" in INPUTRC,
- using a TERM setting like TERM=dumb, and
- building gdb with stub-termcap.
Using a trigger patch in default_gdb_init that adds
"set horizontal-scroll-mode on" to INPUTRC:
...
- setenv INPUTRC [cached_file inputrc "set enable-bracketed-paste off"]
+ setenv INPUTRC [cached_file inputrc "set enable-bracketed-paste off\nset horizontal-scroll-mode on"]
...
we can easily reproduce a failure in gdb.tui/wrap-line.exp mentioned in
PR testsuite/31201 (which was reported for the stub-termcap case):
...
WARNING: timeout in accept_gdb_output
Screen Dump (size 50 columns x 24 rows, cursor at column 34, row 1):
0 Quit
1 <89012345678901234567890123456789W
2
...
23
FAIL: gdb.tui/wrap-line.exp: width-hard-coded: cli: wrap
...
Fix this by accepting the horizontal-scroll-mode style output. We do
this only when in CLI mode though, when in TUI wrapping works as before
because it doesn't rely on readline.
Tested on x86_64-linux.
Co-Authored-By: Tom de Vries <tdevries@suse.de>
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31201
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions