From: "Frank Ch. Eigler" <fche@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: Mark Wielaard <mark@klomp.org>,
dwz@sourceware.org, elfutils-devel@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: build-ids, .debug_sup and other IDs
Date: Thu, 25 Feb 2021 11:42:45 -0500 [thread overview]
Message-ID: <20210225164245.GC11313@redhat.com> (raw)
In-Reply-To: <87a6rt1b12.fsf@tromey.com>
Hi -
> FWIW I looked a little at unifying these. For example,
> bfdopncls.c:bfd_get_alt_debug_link_info could look at both the build-id
> and .debug_sup.
>
> But, this seemed a bit weird. What if both appear and they are
> different? Then a single API isn't so great -- you want to check the ID
> corresponding to whatever was in the original file.
If both appear and are different, can we characterize the elf file as
malformed? Does our current tooling produce such files? If it's an
abnormality (requires special elf manipulation or whatever), we could
avoid bending backward for this case, and tune the tools to the
Normal.
> [...]
> I suppose a distro can ensure that the IDs are always equal.
Via debugedit for example?
> Maybe debuginfod could also just require this.
Or debuginfod could export the content under -both- IDs, if there were
two valid candidates, and just go with the flow. Let the clients
choose which ID they prefer to look up by.
- FChE
next prev parent reply other threads:[~2021-02-25 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210221231810.1062175-1-tom@tromey.com>
2021-02-24 15:07 ` build-ids, .debug_sup and other IDs (Was: [PATCH] Handle DWARF 5 separate debug sections) Mark Wielaard
2021-02-24 17:00 ` Nick Clifton
2021-02-24 17:21 ` Mark Wielaard
2021-02-25 17:52 ` Nick Clifton
2021-06-14 5:52 ` Matt Schulte
2021-06-14 12:49 ` Frank Ch. Eigler
2021-06-14 15:18 ` Matt Schulte
2021-02-24 20:11 ` build-ids, .debug_sup and other IDs Tom Tromey
2021-02-25 16:42 ` Frank Ch. Eigler [this message]
2021-02-25 16:48 ` Jakub Jelinek
2021-02-25 17:04 ` Frank Ch. Eigler
2021-03-02 22:05 ` Tom Tromey
2021-03-02 22:04 ` Tom Tromey
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=20210225164245.GC11313@redhat.com \
--to=fche@redhat.com \
--cc=dwz@sourceware.org \
--cc=elfutils-devel@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=tom@tromey.com \
/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).