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 symtab/30871] [gdb/symtab] Means to control finding debuginfo (without/with sysroot prefix)
Date: Wed, 22 May 2024 14:04:03 +0000 [thread overview]
Message-ID: <bug-30871-4717-sc6jI7LdIj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30871-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30871
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Andrew Burgess from comment #2)
> 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.
Hi Andrew,
I think you're right, a new (maintenance) command isn't necessary to test the
behaviour.
I think I conflated two ideas in this PR:
- IWBN to have a command to show and control how debuginfo is found,
determining
allowed methods (build-id/debug-link/both, with/without sysroot/both) and
order in which they're tried.
- a test-case for finding debuginfo via the sysroot is missing
When filing the PR I thought of the test-case in terms of using the command.
But it's also possible to write a test-case to check one scenario by making
sure the other scenarios will fail, which I suppose is what you have done in
the patch series.
Anyway, I'll take a look at the series, thanks for taking care of the missing
test-case.
You mention extending the test-case, and one thing I can think of that is
nice-to-have, is using symlinks, in other words exercising PR30866 and adding a
KFAIL for that.
As for the command, AFAIC it's a nice-to-have which could be useful. For
instance, my guess is that users who set up debug info on the sysroot might
want to have a means to skip trying to look up debug packages without the
sysroot prefix. But if there's no demand for it, I'm more than happy to drop
it.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-05-22 14:04 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
2024-05-22 14:04 ` vries at gcc dot gnu.org [this message]
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-sc6jI7LdIj@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: link
Be 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).