From: "Frank Ch. Eigler" <fche@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, 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 12:04:40 -0500 [thread overview]
Message-ID: <20210225170440.GD11313@redhat.com> (raw)
In-Reply-To: <20210225164840.GJ4020736@tucnak>
Hi -
> For dwz --dwarf-5, if it produced a .note.gnu.build-id, it would produce
> the same one, but I thought that if I produced that, then consumers could
> keep using that instead of .debug_sup which is the only thing defined
> in the standard, so in the end dwz --dwarf-5 only produces .debug_sup
> on both the referrers side and on the side of supplemental object file
> as DWARF specifies.
Right, but build-ids are still in normal binaries -- just not the
dwz-commonized files created by "dwz --dwarf-5"? So our toolchains
still process build-ids routinely for all the other uses. By omitting
the build-id on the dwz-generated files, we're forcing a flag day on
all our consumer tools. (Does dwz'd dwarf5 even work on gdb
etc. now?) ISTM tool backward compatibility is more important, so
I would suggest dwz generate -both- identifiers.
- FChE
next prev parent reply other threads:[~2021-02-25 17:04 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
2021-02-25 16:48 ` Jakub Jelinek
2021-02-25 17:04 ` Frank Ch. Eigler [this message]
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=20210225170440.GD11313@redhat.com \
--to=fche@redhat.com \
--cc=dwz@sourceware.org \
--cc=elfutils-devel@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jakub@redhat.com \
--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).