From: Mark Wielaard <mark@klomp.org>
To: Tom de Vries <tdevries@suse.de>
Cc: dwz@sourceware.org, nickc@redhat.com
Subject: Re: [PATCH][testsuite] Handle readelf following links by default
Date: Mon, 01 Mar 2021 13:50:54 +0100 [thread overview]
Message-ID: <145415c2190b239da6ea62072eb6bfa5a8ceb74f.camel@klomp.org> (raw)
In-Reply-To: <20210228152134.GH3014@wildebeest.org>
Hi,
On Sun, 2021-02-28 at 16:21 +0100, Mark Wielaard wrote:
> I think this is an odd bug in binutils. --debug-dump=follow-links
> seems to confuses two separate concepts. First whether or not to show
> data that might be stored in a "linked" file. Like whether to show a
> DW_FORM_GNU_alt_strp value. This seems fine and should indeed be done
> by default (that is also what eu-readelf does).
>
> Second whether to dump whole sections from the linked files. That is
> IMHO something completely different and causes the bug you filed. This
> second use should not be the default. And probably should be called
> something different, maybe --debug-dump=dump-links.
>
> Since this is luckily not yet in any released binutils lets fix this
> in binutils instead of trying to work around it in dwz. I am pretty
> sure it will break various other testsuites that rely on binutils
> readelf --debug-dump output if it suddenly also dumped sections from
> other files by default.
Found the thread on the binutils list where Nick is asking for feedback:
https://sourceware.org/pipermail/binutils/2021-March/115582.html
Lets continue the discussion there.
Cheers,
Mark
prev parent reply other threads:[~2021-03-01 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 7:36 Tom de Vries
2021-02-28 15:21 ` Mark Wielaard
2021-03-01 12:50 ` Mark Wielaard [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=145415c2190b239da6ea62072eb6bfa5a8ceb74f.camel@klomp.org \
--to=mark@klomp.org \
--cc=dwz@sourceware.org \
--cc=nickc@redhat.com \
--cc=tdevries@suse.de \
/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).