public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "byron.c.hawkins at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/29146] New: TUI disassembly with long symbols is unreadable, impossible to scroll horizontally
Date: Fri, 13 May 2022 18:21:38 +0000	[thread overview]
Message-ID: <bug-29146-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29146
           Summary: TUI disassembly with long symbols is unreadable,
                    impossible to scroll horizontally
           Product: gdb
           Version: 11.2
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: tui
          Assignee: unassigned at sourceware dot org
          Reporter: byron.c.hawkins at gmail dot com
  Target Milestone: ---

Created attachment 14101
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14101&action=edit
screenshot of the error

With `set print symbol off` in TUI mode layout ASM, GDB continues to print
symbols in the disassembly pane. When the symbol names are long, the opcodes
and operands are pushed off the right of the screen where they are totally
invisible. There is zero mechanism whatsoever to scroll right. 

The symbols are useless here. Notice how the same symbol is printed on every
line. If it is absolutely necessary to print the symbol somewhere, you may
consider printing it once. It is not a reasonable idea to print the symbol on
every line. The code for this feature should be permanently removed.

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

             reply	other threads:[~2022-05-13 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 18:21 byron.c.hawkins at gmail dot com [this message]
2022-05-14 13:23 ` [Bug tui/29146] " ssbssa at sourceware dot org
2022-05-14 18:02 ` tromey at sourceware dot 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-29146-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).