This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
objdump -d / -D behavior
- From: Bryce Schober <bryce dot schober at gmail dot com>
- To: binutils at sources dot redhat dot com
- Date: Fri, 7 Oct 2005 10:58:34 -0700
- Subject: objdump -d / -D behavior
- Reply-to: Bryce Schober <bryce dot schober at gmail dot com>
First, I'm using:
$ arm-elf-objdump -V
GNU objdump 2.16.1
I'm a bit cunfused about the relative behavior of objdump -d vs.
objdump -D. It seems like the implementation is not what the user
would want (read: not what I want). When I use -d, the disassembler is
smart enough not to disassemble non-executable objects, but instead
does a hex dump. When I use -D (because I want to include all sections
in the disassembly), it loses this intelligence. I see no reason why
this should be necessary, or at least if it is necessary to force
disassembly of all data, to have an option that does include sections
with no executable, AND does a hex dump of non-executable sections /
objects.
--
Bryce Schober