public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Maxim Dementyev <mdementyev@fluendo.com>
Cc: binutils@sourceware.org
Subject: Re: readelf --string-dump analog for objdump
Date: Mon, 22 Jan 2024 13:19:05 +0100	[thread overview]
Message-ID: <c656cc81-d612-462b-bfb2-05230486d41e@suse.com> (raw)
In-Reply-To: <CAGp1TcE42t3e6JCKYAcGt+Bhdepe7qmSYhmQmL6EOJBJxmyCxQ@mail.gmail.com>

On 22.01.2024 13:11, Maxim Dementyev wrote:
> 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.

But you're aware of objcopy's --output-target option, by using of which
you could have it produce a raw binary output file?

> 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"

Maybe. Plain "stdout" would be at risk of being ambiguous though. Then
again the use of '=' there is making the whole construct ambiguous
already, for '=' potentially (even if unlikely) being part of the
section name.

Jan

  reply	other threads:[~2024-01-22 12:19 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
2024-01-22 12:19     ` Jan Beulich [this message]
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=c656cc81-d612-462b-bfb2-05230486d41e@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=mdementyev@fluendo.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).