From: Maxim Dementyev <mdementyev@fluendo.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: readelf --string-dump analog for objdump
Date: Mon, 22 Jan 2024 13:11:57 +0100 [thread overview]
Message-ID: <CAGp1TcE42t3e6JCKYAcGt+Bhdepe7qmSYhmQmL6EOJBJxmyCxQ@mail.gmail.com> (raw)
In-Reply-To: <ac6c8893-0c42-46f8-ba39-0ef006290047@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2135 bytes --]
Dear Jan,
Thanks for pointing me out the objdump utility!
Unfortunately, --only-section isn't a good choice: it produces all other
information in the output file, not only the section in question.
But I've found the need option of objdump utility: --dump-section
Unfortunately, apart from this, again, the objdump utility creates a
formatted file as an output, and I can add --only-section to reduce the
size of it and redirect it to /dev/null.
So, this is usable with one intermediate file for a section.
But it is much more complicated than just:
"readelf -p section file | grep something".
And a possible solution (how to improve the objdump utility in a generic
way) could be a special value for the --dump-section option to produce the
output only for this section instead of redirecting it to a separate file:
"objcopy --dump-section section=stdout | grep something"
Thanks again!
With respect,
Max
On Mon, Jan 22, 2024 at 11:58 AM Jan Beulich <jbeulich@suse.com> wrote:
> On 22.01.2024 11:43, Maxim Dementyev wrote:
> > The readelf utility has a very useful option - "--string-dump=<number or
> > name>" which displays the contents of the indicated section as is (as
> > printable strings).
> > As far as I can understand, to do the same with the objdump you need to
> do
> > "objdump --section=<number or name> --full-contents ...".
> > But the output is in the "hexdump" format, the contents is splitted by
> 0x10
> > size blocks (so, not possible to grep on this contents).
> >
> > Is there any plans to implement a printable strings format for this case
> > for the objdump utility?
> > Or is there a solution without parsing the hexdump format and restoring
> > these printable strings?
>
> From what you write I can only guess that you'd like to use the
> functionality
> on non-ELF objects which binutils as whole (and maybe objdump in
> particular)
> supports. If so, is there a reason you can't extract the section(s) in
> question using "objcopy --only-section" (e.g. as a raw binary file), and
> then
> use "strings" on the result?
>
> Jan
>
--
next prev parent reply other threads:[~2024-01-22 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 10:43 Maxim Dementyev
2024-01-22 10:58 ` Jan Beulich
2024-01-22 12:11 ` Maxim Dementyev [this message]
2024-01-22 12:19 ` Jan Beulich
2024-01-22 17:19 ` Maxim Dementyev
2024-01-23 7:41 ` Jan Beulich
2024-01-22 17:42 ` Nick Clifton
2024-01-22 18:03 ` Maxim Dementyev
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=CAGp1TcE42t3e6JCKYAcGt+Bhdepe7qmSYhmQmL6EOJBJxmyCxQ@mail.gmail.com \
--to=mdementyev@fluendo.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).