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/30823] [gdb/tui] segfault in tui_find_disassembly_address Date: Tue, 05 Sep 2023 14:20:16 +0000 [thread overview] Message-ID: <bug-30823-4717-0OQcHiXNKs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30823-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30823 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- With some inspiration from PR27593, I managed to reproduce. Start gdb with rustc binary: ... $ gdb -q -iex "set pagination off" /usr/bin/rustc -ex "set breakpoint pending on" -ex "b dl_main" -ex run -ex "up 4" -ex "layout asm" -ex "print \$pc" ... <TUI> ... $1 = (void (*)()) 0x1 (gdb) ... Now press <up>, and the segfault triggers. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-05 14:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-04 14:05 [Bug tui/30823] New: " vries at gcc dot gnu.org 2023-09-05 14:20 ` vries at gcc dot gnu.org [this message] 2023-09-05 15:05 ` [Bug tui/30823] " vries at gcc dot gnu.org 2023-09-28 18:17 ` cvs-commit at gcc dot gnu.org 2023-09-28 18:18 ` vries at gcc dot gnu.org 2023-09-28 18:18 ` 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-30823-4717-0OQcHiXNKs@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).