public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "edd at theunixzoo dot co.uk" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/26024] New: Cannot scroll up in asm view Date: Fri, 22 May 2020 13:38:20 +0000 [thread overview] Message-ID: <bug-26024-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26024 Bug ID: 26024 Summary: Cannot scroll up in asm view Product: gdb Version: 9.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: edd at theunixzoo dot co.uk Target Milestone: --- Hi, As others have noted too [0], in certain cases you cannot scroll up using the up arrow key when in the asm layout. It seems to me that the bug manifests once the program being debugged has crashed with SIGSEGV. Suppose a.c is a buggy program like: ``` #include <stdio.h> #include <stdlib.h> int main(int argc, char **argv) { printf("%s\n", (char *)0); return (EXIT_SUCCESS); } ``` Now we debug it: ``` $ gcc -g a.c $ gdb a.out ... (gdb) layout asm ``` Now verify that scrolling up and down both work. They do. ``` (gdb) run Starting program: /tmp/a.out Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7f5a181 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 ``` Now scrolling down works, but up does not. This is particularly acute, as you usually want to see what instructions lead to the crash. I'm using version 9.1 but bug seems also present in 8.2.1, as distributed with debian. Thanks [0] https://stackoverflow.com/questions/26572805/gdb-tui-scroll-assembly-view-above-current-instruction -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-05-22 13:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-22 13:38 edd at theunixzoo dot co.uk [this message] 2020-06-25 19:40 ` [Bug tui/26024] " magiblot at hotmail dot com 2021-03-17 10:58 ` edd at theunixzoo dot co.uk
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-26024-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).