From: Alan Modra <amodra@bigpond.net.au>
To: Nick Clifton <nickc@redhat.com>
Cc: "H. J. Lu" <hjl@lucon.org>, Andreas Schwab <schwab@suse.de>,
binutils@sources.redhat.com
Subject: Re: PATCH: Add -N to readelf to display section name
Date: Fri, 01 Apr 2005 11:13:00 -0000 [thread overview]
Message-ID: <20050401111316.GI27909@bubble.modra.org> (raw)
In-Reply-To: <424D28BB.80104@redhat.com>
On Fri, Apr 01, 2005 at 11:55:55AM +0100, Nick Clifton wrote:
> Hi Guys,
>
> >>>>It is very annoying that readelf won't display full section names. This
>
> I realise that the patch has already been applied, but it seems to me
> that adding a new switch to control the displaying of the full section
> name is wrong - I think that this ought to be controlled by the already
> existing "--wide" switch. ie if you specify --wide on the command line
> you get the full section names and wider-than-80-character output,
> whereas if you omit the switch you get possibly truncated section names
> and restricted-to-a-maximum-of-80-characters output.
I think this was discussed before, with someone making a point that
--wide is supposed to not split output lines. HJ's patch puts the
section name on a separate line.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-04-01 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050331210639.GA9469@lucon.org>
[not found] ` <jebr8zfrea.fsf@sykes.suse.de>
[not found] ` <20050331225627.GA11433@lucon.org>
[not found] ` <20050331234925.GB20449@bubble.modra.org>
2005-04-01 10:59 ` Nick Clifton
2005-04-01 11:13 ` Alan Modra [this message]
2005-04-01 11:28 ` Nick Clifton
2005-04-01 14:45 ` H. J. Lu
2005-04-01 15:07 ` Nick Clifton
2005-04-01 14:49 ` PATCH: Document readelf -g H. J. Lu
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=20050401111316.GI27909@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=nickc@redhat.com \
--cc=schwab@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).