Re: [PATCH 1/3] [gdb/tui] Keep inferior output in cmd window with ^L

[Tom de Vries <tdevries@suse.de>]

On 5/31/23 16:27, Bruno Larsen wrote:
> On 31/05/2023 16:19, Tom de Vries wrote:
>> On 5/31/23 15:35, Bruno Larsen wrote:
>>> I can confirm that this fixes the issue you mentioned when the 
>>> terminal scrolls. The problem is that now, if the output doesn't 
>>> cause the screen to scroll, it doesn't show up on screen at all.
>>
>> Is it possible that you're talking about a pre-existing issue?
>>
>> That is, we have:
>> ...
>> (gdb) next
>> ...
>> and after <enter> we have very, very briefly:
>> ...
>> (gdb) next<enter>
>> hello
>> ...
>> before the prompt overwrites it:
>> ...
>> (gdb) next<enter>
>> (gdb)
>> ...
>>
>> I get this behaviour with and without the patch series.  AFAIU, the 
>> only way to deal with this (that doesn't go all the way into 
>> introducing pseudo-terminals) is by introducing a separate cmd and 
>> output window in TUI.  Alternatively, we can move the prompt to the 
>> bottom of the command window, I've spent a day or so trying to make 
>> that work, but abandoned that.
>>
>> If this is not the behaviour you're talking about, please describe a 
>> way of reproducing what you observe.
> 
> Huh... I think I remember this not happening last time I tried using the 
> TUI, which would have been almost 2 years ago. I wonder if I am 
> misremembering, if this use case never came up or if it is an actual 
> regression... 
Reproduced with (using in-repo readline instead of system readline, to 
eliminate a constant system readline as source of non-regression):
- gdb-13-branch
- gdb-12-branch
- gdb-11-branch
- gdb-10-branch
- gdb-9-branch
- gdb-8.3-branch
- gdb-8.2-branch
- gdb-8.1-branch (*)
- gdb-8.0-branch (*) (**)

So, if there is a regression, we're not talking about a recent one 
(8.0.1 released 2017-09-05).

Thanks,
- Tom

(*) Using backport of commit 5a6c3296a7a ("gdb: Fix ia64 defining 
TRAP_HWBKPT before including gdb_wait.h") to fix build.
(**) Without libipt to fix build.