public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "adrianh.bsc at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/15580] New: TUI assembly window line prefix is too long Date: Wed, 05 Jun 2013 14:27:00 -0000 [thread overview] Message-ID: <bug-15580-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15580 Bug ID: 15580 Summary: TUI assembly window line prefix is too long Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: adrianh.bsc at gmail dot com When the assembly window is displayed, it prefixes each line with a fully resolved C++ function signature and line offset which can be very long as it can contain namespaces and template parameters. This is ok, except that it makes it difficult to read the assembly instructions as I have to set the ASM window focus and then scroll right. There are a couple of different suggestions that I have for this: 1. Have the assembly window right justify it's instructions. This will allow the assembly instructions to always be displayed, yet almost always allow the right most portion of the signature and offset to be displayed. 2. Have an alternative prefix which could include be a <filename>:<line> prefix or <filename>:<line>+<offset> for something similar to the <function signature>+<offset> prefix. I'm thinking that the first would require the least amount of changes, but the second may be useful, perhaps in combination with the first. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-06-05 14:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-05 14:27 adrianh.bsc at gmail dot com [this message] 2013-06-05 15:24 ` [Bug tui/15580] " adrianh.bsc at gmail dot com 2022-05-14 18:02 ` tromey at sourceware dot org 2023-06-17 17:38 ` tromey at sourceware dot org 2023-07-11 15:35 ` 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-15580-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: linkBe 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).