public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31256] [14 regression] Crash with basic 'list .' Date: Thu, 18 Jan 2024 18:39:22 +0000 [thread overview] Message-ID: <bug-31256-4717-NT34gZ9p79@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31256-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31256 Sam James <sam at gentoo dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blarsen at redhat dot com --- Comment #1 from Sam James <sam at gentoo dot org> --- The original reporter Christopher Fore has bisected it to commit 3e3a1874fcec34bcf51b4baf4be09aebab561bff Author: Bruno Larsen <blarsen@redhat.com> Date: Thu Jun 15 12:14:22 2023 +0200 gdb/cli: add '.' as an argument for 'list' command Currently, after the user has used the list command once, there is no self-contained way to ask GDB to print the location where the inferior is stopped. The current best options require either using a separate command to scope out where the inferior is stopped, or using "list *$pc" requiring knowledge of GDB standard registers. This commit adds a way to do that using '.' as a new argument for the 'list' command. If the inferior isn't running, the command prints around the main function. Because this necessitated having the inferior running and the test was (seemingly unnecessarily) using printf in a non-essential way and it would make the resulting log harder to read for no benefit, it was replaced by a different statement. Reviewed-By: Eli Zaretskii <eliz@gnu.org> Approved-By: Tom Tromey <tom@tromey.com> .. which added the feature -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-18 18:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 4:57 [Bug gdb/31256] New: " sam at gentoo dot org 2024-01-18 18:26 ` [Bug gdb/31256] " ssbssa at sourceware dot org 2024-01-18 18:39 ` sam at gentoo dot org [this message] 2024-01-18 19:43 ` csfore at posteo dot net 2024-01-18 22:33 ` csfore at posteo dot net 2024-01-19 8:44 ` [Bug gdb/31256] " blarsen at redhat dot com 2024-01-23 15:19 ` blarsen at redhat dot com 2024-01-23 15:43 ` csfore at posteo dot net 2024-01-23 15:59 ` cvs-commit at gcc dot gnu.org 2024-01-23 16:10 ` blarsen at redhat dot com 2024-01-23 16:25 ` cvs-commit at gcc dot gnu.org 2024-02-11 4:42 ` brobecker at gnat dot com
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-31256-4717-NT34gZ9p79@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).