public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hikari at noyu dot me" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/30234] New: Can't scroll up in asm view when remote debugging Date: Wed, 15 Mar 2023 10:20:20 +0000 [thread overview] Message-ID: <bug-30234-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30234 Bug ID: 30234 Summary: Can't scroll up in asm view when remote debugging Product: gdb Version: 13.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: hikari at noyu dot me Target Milestone: --- I'm using GDB to connect to an application that has a primitive implementation of the GDB Remote Serial Protocol. I'm using GDB 13.1 and the architecture is set to ARMv6. If I wait until execution stops at a breakpoint or segfault, and then open the disassembly view with the `layout asm` command, I get a view that I can scroll down, but not up. So I can advance past the instruction where the stop happened, but not backwards. This only happens when there's no file loaded, and thus no symbols. I suspect GDB is confused by not having a symbol as a reference point. If I load a file, even one that apparently only has one symbol (`start`), there's no such problem. I can manually reset the view's position using the disass command with a range of addresses, so it's not as if GDB couldn't disassemble backwards if it wanted to? Looking at the packets sent and received, it seems that GDB is not even trying to read the memory for earlier instructions. No packets seem to be sent or received when pressing the up arrow key. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-03-15 10:20 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-15 10:20 hikari at noyu dot me [this message] 2023-03-15 10:21 ` [Bug tui/30234] " luis.machado at arm dot com 2023-07-11 15:37 ` 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-30234-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).