.... Set up some character translations and predefined strings. \*(-- will
\fIobjfile... are the object files to be examined. When you specify archives, objdump shows information on each of the member object files.
0
If any of the objfile files are archives, display the archive header information (in a format similar to ls -l). Besides the information you could list with ar tv, objdump -a shows the object file format of each archive member.
0
Specify that the object-code format for the object files is \fIbfdname. This option may not be necessary; objdump can automatically recognize many formats. .Sp For example, .Sp .Vb 1 objdump -b oasys -m vax -h fu.o .Ve .Sp displays summary information from the section headers (-h) of \fIfu.o, which is explicitly identified (-m) as a \s-1VAX\s0 object file in the format produced by Oasys compilers. You can list the formats available with the -i option.
0
Decode (demangle) low-level symbol names into user-level names. Besides removing any initial underscore prepended by the system, this makes \*(C+ function names readable. Different compilers have different mangling styles. The optional demangling style argument can be used to choose an appropriate demangling style for your compiler.
0
Display debugging information. This attempts to parse \s-1STABS\s0 and \s-1IEEE\s0 debugging format information stored in the file and print it out using a C like syntax. If neither of these formats are found this option falls back on the -W option to print any \s-1DWARF\s0 information in the file.
0
Like -g, but the information is generated in a format compatible with ctags tool.
0
Display the assembler mnemonics for the machine instructions from \fIobjfile. This option only disassembles those sections which are expected to contain instructions.
0
Like -d, but disassemble the contents of all sections, not just those expected to contain instructions. .Sp If the target is an \s-1ARM\s0 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.
0
Specify the endianness of the object files. This only affects disassembly. This can be useful when disassembling a file format which does not describe endianness information, such as S-records.
0
Display summary information from the overall header of each of the objfile files.
0
When disassembling sections, whenever a symbol is displayed, also display the file offset of the region of data that is about to be dumped. If zeroes are being skipped, then when disassembly resumes, tell the user how many zeroes were skipped and the file offset of the location from where the disassembly resumes. When dumping sections, display the file offset of the location from where the dump starts.
0
Display summary information from the section headers of the object file. .Sp File segments may be relocated to nonstandard addresses, for example by using the -Ttext, -Tdata, or -Tbss options to \fBld. 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.
0
Print a summary of the options to objdump and exit.
0
Display a list showing all architectures and object formats available for specification with -b or -m.
0
Display information only for section name.
0
Label the display (using debugging information) with the filename and source line numbers corresponding to the object code or relocs shown. Only useful with -d, -D, or -r.
0
Specify the architecture to use when disassembling object files. This can be useful when disassembling object files which do not describe architecture information, such as S-records. You can list the available architectures with the -i option. .Sp If the target is an \s-1ARM\s0 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.
0
Pass target specific information to the disassembler. Only supported on some targets. If it is necessary to specify more than one disassembler option then multiple -M options can be used or can be placed together into a comma separated list. .Sp If the target is an \s-1ARM\s0 architecture then this switch can be used to select which register name set is used during disassembler. Specifying \fB-M reg-names-std (the default) will select the register names as used in \s-1ARM\s0's instruction set documentation, but with register 13 called 'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying \fB-M reg-names-apcs will select the name set used by the \s-1ARM\s0 Procedure Call Standard, whilst specifying -M reg-names-raw will just use r followed by the register number. .Sp There are also two variants on the \s-1APCS\s0 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). .Sp This option can also be used for \s-1ARM\s0 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. .Sp 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. \fBx86-64, i386 and i8086 select disassembly for the given architecture. intel and att select between intel syntax mode and \s-1AT&T\s0 syntax mode. \fBintel-mnemonic and att-mnemonic select between intel mnemonic mode and \s-1AT&T\s0 mnemonic mode. intel-mnemonic implies intel and att-mnemonic implies att. \fBaddr64, addr32, \fBaddr16, data32 and data16 specify the default address size and operand size. These four options will be overridden if \fBx86-64, i386 or i8086 appear later in the option string. Lastly, suffix, when in \s-1AT&T\s0 mode, instructs the disassembler to print a mnemonic suffix even when the suffix could be inferred by the operands. .Sp For PowerPC, booke controls the disassembly of BookE instructions. 32 and 64 select PowerPC and PowerPC64 disassembly, respectively. e300 selects disassembly for the e300 family. 440 selects disassembly for the PowerPC 440. ppcps selects disassembly for the paired single instructions of the \s-1PPC750CL\s0. .Sp For \s-1MIPS\s0, 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: Item "no-aliases" Print the 'raw' instruction mnemonic instead of some pseudo instruction mnemonic. I.e., print 'daddu' or 'or' instead of 'move', 'sll' instead of 'nop', etc. Item "gpr-names=ABI" Print \s-1GPR\s0 (general-purpose register) names as appropriate for the specified \s-1ABI\s0. By default, \s-1GPR\s0 names are selected according to the \s-1ABI\s0 of the binary being disassembled. Item "fpr-names=ABI" Print \s-1FPR\s0 (floating-point register) names as appropriate for the specified \s-1ABI\s0. By default, \s-1FPR\s0 numbers are printed rather than names. Item "cp0-names=ARCH" Print \s-1CP0\s0 (system control coprocessor; coprocessor 0) register names as appropriate for the \s-1CPU\s0 or architecture specified by \fI\s-1ARCH\s0. By default, \s-1CP0\s0 register names are selected according to the architecture and \s-1CPU\s0 of the binary being disassembled. Item "hwr-names=ARCH" Print \s-1HWR\s0 (hardware register, used by the \*(C`rdhwr\*(C' instruction) names as appropriate for the \s-1CPU\s0 or architecture specified by \fI\s-1ARCH\s0. By default, \s-1HWR\s0 names are selected according to the architecture and \s-1CPU\s0 of the binary being disassembled. Item "reg-names=ABI" Print \s-1GPR\s0 and \s-1FPR\s0 names as appropriate for the selected \s-1ABI\s0. Item "reg-names=ARCH" Print CPU-specific register names (\s-1CP0\s0 register and \s-1HWR\s0 names) as appropriate for the selected \s-1CPU\s0 or architecture. .Sp For any of the options listed above, \s-1ABI\s0 or \fI\s-1ARCH\s0 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 \s-1ABI\s0 and \s-1ARCH\s0 using the --help option. .Sp For \s-1VAX\s0, you can specify function entry addresses with -M entry:0xf00ba. You can use this multiple times to properly disassemble \s-1VAX\s0 binary files that don't contain symbol tables (like \s-1ROM\s0 dumps). In these cases, the function entry mask would otherwise be decoded as \s-1VAX\s0 instructions, which would probably lead the rest of the function being wrongly disassembled.
0
Print information that is specific to the object file format. The exact information printed depends upon the object file format. For some object file formats, no additional information is printed.
0
Print the relocation entries of the file. If used with -d or \fB-D, the relocations are printed interspersed with the disassembly.
0
Print the dynamic relocation entries of the file. This is only meaningful for dynamic objects, such as certain types of shared libraries. As for -r, if used with -d or \fB-D, the relocations are printed interspersed with the disassembly.
0
Display the full contents of any sections requested. By default all non-empty sections are displayed.
0
Display source code intermixed with disassembly, if possible. Implies \fB-d.
0
Displays the contents of the debug sections in the file, if any are present. If one of the optional letters or words follows the switch then only data found in those specific sections will be dumped. .Sp Note that there is no single letter option to display the content of trace sections.
0
Display the full contents of any sections requested. Display the contents of the .stab and .stab.index and .stab.excl sections from an \s-1ELF\s0 file. This is only useful on systems (such as Solaris 2.0) in which \f(CW\*(C`.stab\*(C' debugging symbol-table entries are carried in an \s-1ELF\s0 section. In most other file formats, debugging symbol-table entries are interleaved with linkage symbols, and are visible in the --syms output.
0
Print the symbol table entries of the file. This is similar to the information provided by the nm program, although the display format is different. The format of the output depends upon the format of the file being dumped, but there are two main types. One looks like this: .Sp .Vb 2 [ 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 .Ve .Sp 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 \fIfl 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. .Sp The other common output format, usually seen with \s-1ELF\s0 based files, looks like this: .Sp .Vb 2 00000000 l d .bss 00000000 .bss 00000000 g .text 00000000 fred .Ve .Sp 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. .Sp 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. .Sp The flag characters are divided into 7 groups as follows: Item "l"
0 Item "g" Item "u" Item "!"
The symbol is a local (l), global (g), unique global (u), neither global nor local (a space) or both global and local (!). A symbol can be neither local or global for a variety of reasons, e.g., because it is used for debugging, but it is probably an indication of a bug if it is ever both local and global. Unique global symbols are a \s-1GNU\s0 extension to the standard set of \s-1ELF\s0 symbol bindings. For such a symbol the dynamic linker will make sure that in the entire process there is just one symbol with this name and type in use. Item "w" The symbol is weak (w) or strong (a space). Item "C" The symbol denotes a constructor (C) or an ordinary symbol (a space). Item "W" The symbol is a warning (W) or a normal symbol (a space). A warning symbol's name is a message to be displayed if the symbol following the warning symbol is ever referenced. Item "I"
0 Item "i"
The symbol is an indirect reference to another symbol (I), a function to be evaluated during reloc processing (i) or a normal symbol (a space). Item "d"
0 Item "D"
The symbol is a debugging symbol (d) or a dynamic symbol (D) or a normal symbol (a space). Item "F"
0 Item "f" Item "O"
The symbol is the name of a function (F) or a file (f) or an object (O) or just a normal symbol (a space).
0
Print the dynamic symbol table entries of the file. This is only meaningful for dynamic objects, such as certain types of shared libraries. This is similar to the information provided by the nm program when given the -D (--dynamic) option.
0
Print the version number of objdump and exit.
0
Display all available header information, including the symbol table and relocation entries. Using -x is equivalent to specifying all of \fB-a -f -h -p -r -t.
0
Format some lines for output devices that have more than 80 columns. Also do not truncate symbol names when they are displayed.
0
Normally the disassembly output will skip blocks of zeroes. This option directs the disassembler to disassemble those blocks, just like any other data.
Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \*(L"\s-1GNU\s0 Free Documentation License\*(R".