From: Nick Clifton <nickc@redhat.com>
To: Katharina Bogad <katharina@bogad.at>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Readelf: --wide as default if output is redirected
Date: Thu, 17 Sep 2020 10:55:25 +0100 [thread overview]
Message-ID: <0c4f8085-3403-4984-e370-f8624c048438@redhat.com> (raw)
In-Reply-To: <C48785C9-6DCC-4C19-8FC7-1A3DD3A3F47C@bogad.at>
Hi Katharina,
> as I spent the last hour or so trying to figure out why some function names
> in the output of readelf -r cannot be found and then realizing that readelf has
> silently truncated them,
Which version of readelf ?
I added a new feature to the 2.35 release so that by default readelf will
suffix truncated symbol names with "[...]", thus letting the reader know
that the name has been abbreviated.
> I was wondering if it was possible to make --wide the
> default if the output is redirected (as I was reading it in a pager anyways).
>
> Now, as this is a pure quality of life improvement, I wanted to speak to someone
> before submitting a patch. I know that changing any API, especially in a tool
> as widely used like binutils is a huge deal, but I want to discuss this anyways.
Yeah, I think that changing the default behaviour like this would be a bad
idea. But of course you can always create a wrapper script that adds the --wide
option (and maybe invokes the pager at the same time).
Cheers
Nick
next prev parent reply other threads:[~2020-09-17 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 16:06 Katharina Bogad
2020-09-16 18:01 ` H.J. Lu
2020-09-17 9:55 ` Nick Clifton [this message]
2020-09-17 10:36 ` Katharina Bogad
2020-09-17 15:37 ` Nick Clifton
2020-09-17 15:59 ` Fangrui Song
2020-09-18 13:57 ` Mark Wielaard
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=0c4f8085-3403-4984-e370-f8624c048438@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=katharina@bogad.at \
/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).