[Bug tui/30526] New: [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen

[Bug tui/30526] New: [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30526

            Bug ID: 30526
           Summary: [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tui
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Say we run TUI with TERM=ansi in an xterm:
...
TERM=ansi gdb -q -tui -iex "set tui border-kind ascii"
...
and press ^L to fix the slightly broken screen.

Now, type "echo \n" and press enter until the prompt is at the bottom of the
screen.

Now type tui disable<enter>.

The only thing that changed in the screen is that the cursor moved to the start
of tui disable.  We have in fact left TUI, which we can see by doing ^L which
will clear the entire screen, rather than refresh as it does in TUI.

The fact that we see "tui disable" is the TERM=ansi version of PR30523.

But even if we fix that, there's still no clear sign that we left TUI.

I think we should clear all windows, except the cmd window.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tui/30526] [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30526

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d033023bc4ce9e61fe47172ee451cce2b96cdc98

commit d033023bc4ce9e61fe47172ee451cce2b96cdc98
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Jun 7 11:36:19 2023 +0200

    [gdb/testsuite] Add missing wait in gdb.python/tui-window-disabled.exp

    While working on PR tui/30526, I noticed a bug in test-case
    gdb.python/tui-window-disabled.exp.

    Here we send "tui enable" to gdb, but don't wait for it to arrive before
    checking for a window box:
    ...
        send_gdb "tui enable\n"
        Term::check_box "check for python window" 0 0 80 16
    ...

    Fix this by waiting for the prompt to be issued in TUI before doing the
check.

    Tested on x86_64-linux.

-- 
You are receiving this mail because:
You are on the CC list for the bug.