public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30871] [gdb/symtab] Means to control finding debuginfo (without/with sysroot prefix) Date: Mon, 20 May 2024 14:17:02 +0000 [thread overview] Message-ID: <bug-30871-4717-0KjSUcsnYO@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30871-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30871 Andrew Burgess <aburgess at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aburgess at redhat dot com --- Comment #2 from Andrew Burgess <aburgess at redhat dot com> --- Hi Tom, I was taking a look at this, and I wasn't clear on why we need a new maintenance command? Your point seems solid: there are no tests for finding debug information using the sysroot, but isn't the fix to that just to add such a test? How does the new maintenance command help us? Anyway, I posted this: https://inbox.sourceware.org/gdb-patches/cover.1716214388.git.aburgess@redhat.com As an attempt to address this patch. I can look at extending it if some case isn't being covered sufficiently. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-05-20 14:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-19 8:18 [Bug symtab/30871] New: " vries at gcc dot gnu.org 2023-09-19 9:49 ` [Bug symtab/30871] " vries at gcc dot gnu.org 2024-05-20 14:17 ` aburgess at redhat dot com [this message] 2024-05-22 14:04 ` 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-30871-4717-0KjSUcsnYO@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).