diff options
| author | Tom Tromey <tom@tromey.com> | 2025-06-13 12:54:16 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2025-07-01 15:59:41 -0600 |
| commit | 7b18593a9ef94694e2a16ac25133aa8c19dc6a87 (patch) | |
| tree | 39ea1de8d6a15125c6def31548cbbff359fd6b3a /gdb/python/py-param.c | |
| parent | b054ff604253af016657d5c93e2f69dab14cc53a (diff) | |
| download | binutils-7b18593a9ef94694e2a16ac25133aa8c19dc6a87.zip binutils-7b18593a9ef94694e2a16ac25133aa8c19dc6a87.tar.gz binutils-7b18593a9ef94694e2a16ac25133aa8c19dc6a87.tar.bz2 | |
Fix handling of terminal escape sequences in TUI
A user noticed that if the remote sends terminal escape sequences from
the "monitor" command, then these will not be correctly displayed when
in TUI mode.
I tracked this down to remote.c emitting one character at a time --
something the TUI output functions did not handle correctly.
I decided in the end to fix in this in the ui-file layer, because the
same bug seems to affect logging and, as is evidenced by the test case
in this patch, Python output in TUI mode.
The idea is simple: buffer escape sequences until they are either
complete or cannot possibly be recognized by gdb.
Regression tested on x86-64 Fedora 40.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=14126
Approved-By: Andrew Burgess <aburgess@redhat.com>
Diffstat (limited to 'gdb/python/py-param.c')
0 files changed, 0 insertions, 0 deletions