From: Nick Clifton <nickc@redhat.com>
To: Mark Wielaard <mark@klomp.org>, Tom Tromey <tom@tromey.com>
Cc: dwz@sourceware.org, elfutils-devel@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: build-ids, .debug_sup and other IDs (Was: [PATCH] Handle DWARF 5 separate debug sections)
Date: Wed, 24 Feb 2021 17:00:14 +0000 [thread overview]
Message-ID: <8c0ada00-7516-a7a2-b08e-aaaf677dd4f6@redhat.com> (raw)
In-Reply-To: <20210224150752.GA23884@tarox.wildebeest.org>
Hi Mark,
> Context is that dwz 0.15 (still not released yet) can now produce
> standardized DWARF Supplementary Files using a .debug_sup section
> when using --dwarf-5 -m multifile. See this bug report:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27440
Is there somewhere that I can lay my hands on a file containing a
.debug_sup section and its corresponding supplimentary file ? I
would like to test the binutils to make sure that they can support
them too.
Cheers
Nick
next prev parent reply other threads:[~2021-02-24 17:00 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 ` Mark Wielaard
2021-02-24 17:00 ` Nick Clifton [this message]
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
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=8c0ada00-7516-a7a2-b08e-aaaf677dd4f6@redhat.com \
--to=nickc@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).