objdump [-a|--archive-headers] [-b bfdname|--target=bfdname] [-C|--demangle[=style] ] [-d|--disassemble[=symbol]] [-D|--disassemble-all] [-z|--disassemble-zeroes] [-EB|-EL|--endian={big | little }] [-f|--file-headers] [-F|--file-offsets] [--file-start-context] [-g|--debugging] [-e|--debugging-tags] [-h|--section-headers|--headers] [-i|--info] [-j section|--section=section] [-l|--line-numbers] [-S|--source] [--source-comment[=text]] [-m machine|--architecture=machine] [-M options|--disassembler-options=options] [-p|--private-headers] [-P options|--private=options] [-r|--reloc] [-R|--dynamic-reloc] [-s|--full-contents] [-W[lLiaprmfFsoRtUuTgAckK]| --dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]] [--ctf=section] [-G|--stabs] [-t|--syms] [-T|--dynamic-syms] [-x|--all-headers] [-w|--wide] [--start-address=address] [--stop-address=address] [--prefix-addresses] [--[no-]show-raw-insn] [--adjust-vma=offset] [--dwarf-depth=n] [--dwarf-start=n] [--ctf-parent=section] [--ctf-symbols=section] [--ctf-strings=section] [--no-recurse-limit|--recurse-limit] [--special-syms] [--prefix=prefix] [--prefix-strip=level] [--insn-width=width] [-V|--version] [-H|--help] objfile...
objdump displays information about one or more object files. The options control what particular information to display. This information is mostly useful to programmers who are working on the compilation tools, as opposed to programmers who just want their program to compile and work.
objfile... are the object files to be examined. When you specify archives, objdump shows information on each of the member object files.
The long and short forms of options, shown here as alternatives, are equivalent. At least one option from the list -a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-P,-r,-R,-s,-S,-t,-T,-V,-x must be given.
For example,
objdump -b oasys -m vax -h fu.o
displays summary information from the section headers (-h) of
fu.o, which is explicitly identified (-m) as a VAX object
file in the format produced by Oasys compilers. You can list the
formats available with the -i option.
See Target Selection, for more information.
The default is for this limit to be enabled, but disabling it may be
necessary in order to demangle truly complicated names. Note however
that if the recursion limit is disabled then stack exhaustion is
possible and any bug reports about such an event will be rejected.
Note if the --dwarf=follow-links option has also been enabled
then any symbol tables in linked debug info files will be read in and
used when disassembling.
This option also has a subtle effect on the disassembly of instructions in code sections. When option -d is in effect objdump will assume that any symbols present in a code section occur on the boundary between instructions and it will refuse to disassemble across such a boundary. When option -D is in effect however this assumption is supressed. This means that it is possible for the output of -d and -D to differ if, for example, data is stored in code sections.
If the target is an ARM architecture this switch also has the effect of forcing the disassembler to decode pieces of data found in code sections as if they were instructions.
Note if the --dwarf=follow-links option has also been enabled
then any symbol tables in linked debug info files will be read in and
used when disassembling.
File segments may be relocated to nonstandard addresses, for example by using the -Ttext, -Tdata, or -Tbss options to ld. However, some object file formats, such as a.out, do not store the starting address of the file segments. In those situations, although ld relocates the sections correctly, using ‘objdump -h’ to list the file section headers cannot show the correct addresses. Instead, it shows the usual addresses, which are implicit for the target.
Note, in some cases it is possible for a section to have both the
READONLY and the NOREAD attributes set. In such cases the NOREAD
attribute takes precedence, but objdump will report both
since the exact setting of the flag bits might be important.
If the target is an ARM architecture then this switch has an
additional effect. It restricts the disassembly to only those
instructions supported by the architecture specified by machine.
If it is necessary to use this switch because the input file does not
contain any architecture information, but it is also desired to
disassemble all the instructions use -marm.
For ARC, dsp controls the printing of DSP instructions, spfp selects the printing of FPX single precision FP instructions, dpfp selects the printing of FPX double precision FP instructions, quarkse_em selects the printing of special QuarkSE-EM instructions, fpuda selects the printing of double precision assist instructions, fpus selects the printing of FPU single precision FP instructions, while fpud selects the printing of FPU double precision FP instructions. Additionally, one can choose to have all the immediates printed in hexadecimal using hex. By default, the short immediates are printed using the decimal representation, while the long immediate values are printed as hexadecimal.
cpu=... allows to enforce a particular ISA when disassembling instructions, overriding the -m value or whatever is in the ELF file. This might be useful to select ARC EM or HS ISA, because architecture is same for those and disassembler relies on private ELF header data to decide if code is for EM or HS. This option might be specified multiple times - only the latest value will be used. Valid values are same as for the assembler -mcpu=... option.
If the target is an ARM architecture then this switch can be used to select which register name set is used during disassembler. Specifying -M reg-names-std (the default) will select the register names as used in ARM's instruction set documentation, but with register 13 called 'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying -M reg-names-apcs will select the name set used by the ARM Procedure Call Standard, whilst specifying -M reg-names-raw will just use ‘r’ followed by the register number.
There are also two variants on the APCS register naming scheme enabled by -M reg-names-atpcs and -M reg-names-special-atpcs which use the ARM/Thumb Procedure Call Standard naming conventions. (Either with the normal register names or the special register names).
This option can also be used for ARM architectures to force the disassembler to interpret all instructions as Thumb instructions by using the switch --disassembler-options=force-thumb. This can be useful when attempting to disassemble thumb code produced by other compilers.
For AArch64 targets this switch can be used to set whether instructions are disassembled as the most general instruction using the -M no-aliases option or whether instruction notes should be generated as comments in the disasssembly using -M notes.
For the x86, some of the options duplicate functions of the -m switch, but allow finer grained control. Multiple selections from the following may be specified as a comma separated string.
x86-64
i386
i8086
intel
att
amd64
intel64
intel-mnemonic
att-mnemonic
intel-mnemonic
implies intel
and
att-mnemonic
implies att
.
addr64
addr32
addr16
data32
data16
x86-64
, i386
or i8086
appear later in the option string.
suffix
For PowerPC, the -M argument raw selects
disasssembly of hardware insns rather than aliases. For example, you
will see rlwinm
rather than clrlwi
, and addi
rather than li
. All of the -m arguments for
gas that select a CPU are supported. These are:
403, 405, 440, 464, 476,
601, 603, 604, 620, 7400,
7410, 7450, 7455, 750cl,
821, 850, 860, a2, booke,
booke32, cell, com, e200z4,
e300, e500, e500mc, e500mc64,
e500x2, e5500, e6500, efs,
power4, power5, power6, power7,
power8, power9, ppc, ppc32,
ppc64, ppc64bridge, ppcps, pwr,
pwr2, pwr4, pwr5, pwr5x,
pwr6, pwr7, pwr8, pwr9,
pwrx, titan, and vle.
32 and 64 modify the default or a prior CPU
selection, disabling and enabling 64-bit insns respectively. In
addition, altivec, any, htm, vsx,
and spe add capabilities to a previous or later CPU
selection. any will disassemble any opcode known to
binutils, but in cases where an opcode has two different meanings or
different arguments, you may not see the disassembly you expect.
If you disassemble without giving a CPU selection, a default will be
chosen from information gleaned by BFD from the object files headers,
but the result again may not be as you expect.
For MIPS, this option controls the printing of instruction mnemonic names and register names in disassembled instructions. Multiple selections from the following may be specified as a comma separated string, and invalid options are ignored:
no-aliases
msa
virt
xpa
gpr-names=
ABIfpr-names=
ABIcp0-names=
ARCHhwr-names=
ARCHrdhwr
instruction) names
as appropriate for the CPU or architecture specified by
ARCH. By default, HWR names are selected according to
the architecture and CPU of the binary being disassembled.
reg-names=
ABIreg-names=
ARCHFor any of the options listed above, ABI or ARCH may be specified as ‘numeric’ to have numbers printed rather than names, for the selected types of registers. You can list the available values of ABI and ARCH using the --help option.
For VAX, you can specify function entry addresses with -M
entry:0xf00ba. You can use this multiple times to properly
disassemble VAX binary files that don't contain symbol tables (like
ROM dumps). In these cases, the function entry mask would otherwise
be decoded as VAX instructions, which would probably lead the rest
of the function being wrongly disassembled.
For XCOFF, the available options are:
header
aout
sections
syms
relocs
lineno,
loader
except
typchk
traceback
toc
ldinfo
Not all object formats support this option. In particular the ELF
format does not use it.
Displays the contents of the DWARF debug sections in the file, if any are present. Compressed debug sections are automatically decompressed (temporarily) before they are displayed. If one or more of the optional letters or words follows the switch then only those type(s) of data will be dumped. The letters and words refer to the following information:
a
=abbrev
A
=addr
c
=cu_index
f
=frames
F
=frame-interp
g
=gdb_index
i
=info
k
=links
K
=follow-links
In addition, when displaying DWARF attributes, if a form is found that
references the separate debug info file, then the referenced contents
will also be displayed.
l
=rawline
L
=decodedline
m
=macro
o
=loc
p
=pubnames
r
=aranges
R
=Ranges
s
=str
t
=pubtype
T
=trace_aranges
u
=trace_abbrev
U
=trace_info
Note: displaying the contents of ‘.debug_static_funcs’,
‘.debug_static_vars’ and ‘debug_weaknames’ sections is not
currently supported.
.debug_info
section to n children.
This is only useful with --debug-dump=info. The default is
to print all DIEs; the special value 0 for n will also have this
effect.
With a non-zero value for n, DIEs at or deeper than n
levels will not be printed. The range for n is zero-based.
If specified, this option will suppress printing of any header information and all DIEs before the DIE numbered n. Only siblings and children of the specified DIE will be printed.
This can be used in conjunction with --dwarf-depth.
.stab
debugging symbol-table entries are carried in an ELF
section. In most other file formats, debugging symbol-table entries are
interleaved with linkage symbols, and are visible in the --syms
output.
[ 4](sec 3)(fl 0x00)(ty 0)(scl 3) (nx 1) 0x00000000 .bss [ 6](sec 1)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000 fred
where the number inside the square brackets is the number of the entry in the symbol table, the sec number is the section number, the fl value are the symbol's flag bits, the ty number is the symbol's type, the scl number is the symbol's storage class and the nx value is the number of auxilary entries associated with the symbol. The last two fields are the symbol's value and its name.
The other common output format, usually seen with ELF based files, looks like this:
00000000 l d .bss 00000000 .bss 00000000 g .text 00000000 fred
Here the first number is the symbol's value (sometimes refered to as its address). The next field is actually a set of characters and spaces indicating the flag bits that are set on the symbol. These characters are described below. Next is the section with which the symbol is associated or *ABS* if the section is absolute (ie not connected with any section), or *UND* if the section is referenced in the file being dumped, but not defined there.
After the section name comes another field, a number, which for common symbols is the alignment and for other symbol is the size. Finally the symbol's name is displayed.
The flag characters are divided into 7 groups as follows:
l
g
u
!
w
C
W
I
i
d
D
F
f
O
The output format is similar to that produced by the --syms
option, except that an extra field is inserted before the symbol's
name, giving the version information associated with the symbol.
If the version is the default version to be used when resolving
unversioned references to the symbol then it's displayed as is,
otherwise it's put into parentheses.