public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/30440] [gdb/tui] repeated stepi ends up with garbled screen
Date: Thu, 11 May 2023 16:12:37 +0000	[thread overview]
Message-ID: <bug-30440-4717-fm6w3cXGuI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30440-4717@http.sourceware.org/bugzilla/>

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

--- Comment #13 from Tom de Vries <vries at gcc dot gnu.org> ---
I'm starting to think this is the input variant of PR14332.

By doing stepi, we temporarily hand the terminal to the inferior.

Some of the enters will land in that window where the inferior has the
terminal, and will be handled according to those terminal settings, not the
terminal settings as setup for/by ncurses, and they're probably just translated
into a newline and echoed.

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

  parent reply	other threads:[~2023-05-11 16:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  9:43 [Bug tui/30440] New: " vries at gcc dot gnu.org
2023-05-11  9:45 ` [Bug tui/30440] " vries at gcc dot gnu.org
2023-05-11  9:45 ` vries at gcc dot gnu.org
2023-05-11 10:19 ` vries at gcc dot gnu.org
2023-05-11 10:45 ` vries at gcc dot gnu.org
2023-05-11 10:52 ` vries at gcc dot gnu.org
2023-05-11 12:18 ` vries at gcc dot gnu.org
2023-05-11 13:25 ` vries at gcc dot gnu.org
2023-05-11 13:34 ` vries at gcc dot gnu.org
2023-05-11 13:42 ` vries at gcc dot gnu.org
2023-05-11 13:46 ` vries at gcc dot gnu.org
2023-05-11 13:51 ` vries at gcc dot gnu.org
2023-05-11 14:07 ` vries at gcc dot gnu.org
2023-05-11 16:12 ` vries at gcc dot gnu.org [this message]
2023-05-22 16:24 ` vries at gcc dot gnu.org

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-30440-4717-fm6w3cXGuI@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).