From: Tom Tromey <tom@tromey.com>
To: Paul Smith via Gdb <gdb@sourceware.org>
Cc: psmith@gnu.org
Subject: Re: debuginfod: why can't it save real filenames??
Date: Thu, 05 Nov 2026 09:40:54 -0700 [thread overview]
Message-ID: <8733tfz0x5.fsf@tromey.com> (raw)
In-Reply-To: <be8f2dc957fcfa876247a4ca2b52bc331c77487f.camel@gnu.org> (Paul Smith via Gdb's message of "Wed, 04 Nov 2026 16:06:33 -0500")
>>>>> Paul Smith via Gdb <gdb@sourceware.org> writes:
> Of course, I understand that the directory name is the build ID value
> and that it's how we ensure uniqueness so it's required, but why can't
> the static filename "executable" be changed to the name of the library
> or program that is being represented? Then it would be easy enough to
> understand.
Looking at the gdb code, I think the debuginfod client-side library
decides the file name:
fd = scoped_fd (debuginfod_find_debuginfo (c, build_id, build_id_len,
&dname));
You may get a better answer on the elfutils list, since debuginfo is
part of that project.
thanks,
Tom
prev parent reply other threads:[~2026-11-05 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 21:06 Paul Smith via Gdb
2026-11-05 16:40 ` Tom Tromey [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=8733tfz0x5.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.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