public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/30526] [gdb/tui, TERM=ansi] Exiting tui doesn't clear screen
Date: Wed, 07 Jun 2023 09:36:32 +0000	[thread overview]
Message-ID: <bug-30526-4717-7t7ZuXFqpf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30526-4717@http.sourceware.org/bugzilla/>

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.

      reply	other threads:[~2023-06-07  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  7:10 [Bug tui/30526] New: " vries at gcc dot gnu.org
2023-06-07  9:36 ` cvs-commit at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30526-4717-7t7ZuXFqpf@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).