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] New: [gdb/tui] repeated stepi ends up with garbled screen
Date: Thu, 11 May 2023 09:43:26 +0000	[thread overview]
Message-ID: <bug-30440-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30440
           Summary: [gdb/tui] repeated stepi ends up with garbled 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: ---

I've been playing around with TUI, and tried to find an easy way to do a stress
test.

I came up with starting a hello world, and doing si and then keeping my finger
on the enter key and see what happens.

I eventually ran into screen garbling, which could be repaired using ^L.

I realized this garbling could be the result of printing the "hello", so I
moved to compiling "int main (void) { return 0; }", doing a starti, and
stepi-ing from there.  I played around with this for a while, and found that I
could reproduce the problem within minutes when starting to stepi from
__GI___tunables_init.

I tried to write a test-case that mimics this in the testsuite, but sofar I
didn't manage to reproduce this.

So, here are the steps I followed (this may be way over-specific):
- openSUSE Leap 15.4 x86_64-linux
- gdb build using -O0
- gdb build from commit 38b95a52938 ("Automatic date update in version.in")
- gnome-terminal (on KDE desktop)
- TERM=xterm (native TERM=xterm-256colors)
- tab with COLUMNS 145, LINES 37
- stay in the tab, to avoid ncurses refresh when switching back to the tab.
  This also prevents resetting the regs window layout to one reg on one line.
- gdb started using "gdb ~/a.out"
- starti
- layout asm (enter tui, use asm window)
- layout regs (add regs window)
- stepi (populate regs window, should show two regs on one line)
- b __GI___tunables_init, continue
- stepi (command to repeat)
- press-and-hold enter
- observe garbling and release enter (for me, after about 3/4 minutes)

I've now also reproduce by starting gdb like so:
...
$ gdb -q ~/a.out \
    -ex "starti" \
    -ex "layout asm" \
    -ex "layout regs" \
    -ex "stepi" 
    -ex "b __GI___tunables_init" 
... 
and then continue, stepi, and press-and-hold enter.

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

             reply	other threads:[~2023-05-11  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  9:43 vries at gcc dot gnu.org [this message]
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
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@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).