OBJDUMP(1)

📦 version 12.2.0, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, welcome to OBJDUMP(1), aka the GNU Development Tools page that’s about to make object files make sense. Main character energy only 💅

objdump — display information from object files.

✨ SYNOPSIS ✨

objdump [-a|--archive-headers]
        [-b bfdname|--target=bfdname]
        [-C|--demangle[=style] ]
        [-d|--disassemble]
        [-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]
        [-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]
        [-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]
        [--special-syms]
        [--prefix=prefix]
        [--prefix-strip=level]
        [--insn-width=width]
        [-V|--version]
        [-H|--help]
        objfile...

🦋 DESCRIPTION 🦋

So objdump displays information about one or more object files. The options control what particular information gets shown, and honestly this info is mostly useful to programmers who are working on the compilation tools — not so much for programmers who just want their program to compile and work, y’know?

The objfile... are the object files to be examined. And when you specify archives, objdump shows information on each of the member object files. Cute, thorough, obsessed 🫶

🎀 OPTIONS 🎀

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. Like, pick at least one, bestie 😭

  • -a, --archive-header — 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. Slay.
  • --adjust-vma=offset — when dumping information, first add offset to all the section addresses. This is useful if the section addresses do not correspond to the symbol table, which can happen when putting sections at particular addresses when using a format which can not represent section addresses, such as a.out. Ngl, classic a.out behavior 💀
  • -b bfdname, --target=bfdname — specify that the object-code format for the object files is bfdname. This option may not be necessary; objdump can automatically recognize many formats.

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. Iconic little format check ✨

  • -C, --demangle[=style] — 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. Your fave readability glow-up 💅
  • -g, --debugging — display debugging information. This attempts to parse STABS and IEEE 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 DWARF information in the file. Fallback behavior ate, fr fr 🍓
  • -e, --debugging-tags — like -g, but the information is generated in a format compatible with ctags tool.
  • -d, --disassemble — display the assembler mnemonics for the machine instructions from objfile. This option only disassembles those sections which are expected to contain instructions. No chaotic extra sections, just the expected ones 💖
  • -D, --disassemble-all — like -d, but disassemble the contents of all sections, not just those expected to contain instructions.

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 suppressed. This means that it is possible for the output of -d and -D to differ if, for example, data is stored in code sections. Lowkey important 👑

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.

  • --prefix-addresses — when disassembling, print the complete address on each line. This is the older disassembly format. Vintage but valid 🎀
  • -EB, -EL, --endian={big|little} — 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. Endianness check bestie 🌈
  • -f, --file-headers — display summary information from the overall header of each of the objfile files.
  • -F, --file-offsets — 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. File offset lore, iykyk 🔥
  • --file-start-context — specify that when displaying interlisted source code/disassembly (assumes -S) from a file that has not yet been displayed, extend the context to the start of the file. Context from the very beginning, periodt.
  • -h, --section-headers, --headers — display summary information from the section headers of the object file.

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. Not me learning a.out limits again 😭

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. Flag bit accuracy is the moment 💜

  • -H, --help — print a summary of the options to objdump and exit.
  • -i, --info — display a list showing all architectures and object formats available for specification with -b or -m.
  • -j name, --section=name — display information only for section name. One section, main character only 💅
  • -l, --line-numbers — 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.
  • -m machine, --architecture=machine — 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.

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. ARM girlies know 🧚

  • -M options, --disassembler-options=options — 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.

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.
  • fpud selects the printing of FPU souble 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. Hex mode moment ✨

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.

okay continuing the -M saga, bestie — we were literally mid-sentence, so let's go 💅

🍎 ARM vibes

If your target is an ARM architecture, this switch lets you pick which register name set the disassembler uses.

  • -M reg-names-std (the default) — names exactly like ARM's own instruction set docs, except register 13 is called sp, register 14 is lr, and register 15 is pc.
  • -M reg-names-apcs — the name set used by the ARM Procedure Call Standard.
  • -M reg-names-raw — just r followed by the register number, no frills, no cap.

There's also two variants on the APCS naming scheme:

  • -M reg-names-atpcs — ARM/Thumb Procedure Call Standard naming conventions.
  • -M reg-names-special-atpcs — same, but with the special register names.

(Either with the normal register names or the special ones, iykyk ✨)

Also, for ARM architectures you can force the disassembler to read every instruction as a Thumb instruction:

--disassembler-options=force-thumb

Which is lowkey iconic when you're trying to disassemble thumb code some other compiler coughed up 🫶

💻 x86 (finer-grained control, she's precise)

Some of these duplicate what -m does, but with finer grained control. You can stack multiple picks as a comma separated string.

  • x86-64, i386, i8086 — select disassembly for that architecture.
  • intel, att — pick intel syntax mode vs AT&T syntax mode.
  • amd64, intel64 — pick AMD64 ISA vs Intel64 ISA.
  • intel-mnemonic, att-mnemonic — pick intel mnemonic mode vs AT&T mnemonic mode. > Note: intel-mnemonic implies intel, and att-mnemonic implies att.
  • addr64, addr32, addr16, data32, data16 — set the default address size and operand size. These get overridden if x86-64, i386 or i8086 appear later in the option string. (The page says "these four" while listing five, and honestly? not my problem 🫠 the override rule is the part that matters.)
  • suffix — in AT&T mode, tells the disassembler to print a mnemonic suffix even when the operands would've made it obvious anyway. She's extra, we love her.

🔥 PowerPC

For PowerPC, -M raw selects disassembly of hardware insns rather than aliases. So you'll see rlwinm instead of clrlwi, and addi instead of li. Slay.

Every -m argument for gas that selects a CPU is supported. The full roster, no cap:

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.
  • altivec, any, htm, vsx, and spe — add capabilities to a previous or later CPU selection.
⚠️ any will disassemble any opcode known to binutils, but when an opcode has two different meanings or different arguments, you may not see the disassembly you expected. Same energy if you disassemble without giving a CPU selection — a default gets chosen from info BFD gleaned from the object file headers, and the result again may not be what you expected. It's giving "trust the process" 😭

🐚 MIPS

For MIPS, this option controls how instruction mnemonic names and register names get printed in disassembled instructions. Multiple picks as a comma separated string, and invalid options are just ignored (she's unbothered).

  • 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.
  • msa — disassemble MSA instructions.
  • virt — disassemble the virtualization ASE instructions.
  • xpa — disassemble the eXtended Physical Address (XPA) ASE instructions.
  • gpr-names=ABI — print GPR (general-purpose register) names as appropriate for the specified ABI. By default, GPR names are selected according to the ABI of the binary being disassembled.
  • fpr-names=ABI — print FPR (floating-point register) names as appropriate for the specified ABI. By default, FPR numbers are printed rather than names.
  • cp0-names=ARCH — print CP0 (system control coprocessor; coprocessor 0) register names as appropriate for the CPU or architecture specified by ARCH. By default, CP0 register names are selected according to the architecture and CPU of the binary being disassembled.
  • hwr-names=ARCH — print HWR (hardware register, used by the rdhwr 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=ABI — print GPR and FPR names as appropriate for the selected ABI.
  • reg-names=ARCH — print CPU-specific register names (CP0 register and HWR names) as appropriate for the selected CPU or architecture.

For any of the options up there, ABI or ARCH can be given as a number to get numbers printed instead of names, for the selected types of registers. You can list the available values of ABI and ARCH with the --help option 🎀

🦕 VAX

You can specify function entry addresses like this:

-M entry:0xf00ba

Use it multiple times to properly disassemble VAX binary files that don't contain symbol tables (ROM dumps, bestie, we've all been there). Without it, the function entry mask would be decoded as VAX instructions, which would probably lead to the rest of the function being wrongly disassembled. Not the vibe 💀

the rest of the options, let's keep going 🧚

  • -p, --private-headers — print information specific to the object file format. The exact info depends on the object file format. For some object file formats, no additional information is printed at all (yes, really, she said nothing 🫠).
  • -P options, *--private=options* — print information specific to the object file format. The argument options is a comma separated list that depends on the format (the lists of options is displayed with the help). 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.
  • -r, --reloc — print the relocation entries of the file. If used with -d or -D, the relocations get printed interspersed with the disassembly. Cute little interleaving moment ✨
  • -R, --dynamic-reloc — print the dynamic relocation entries of the file. Only meaningful for dynamic objects, like certain types of shared libraries. As for -r, if used with -d or -D, the relocations get printed interspersed with the disassembly.
  • -s, --full-contents — display the full contents of any sections requested. By default all non-empty sections are displayed.
  • -S, --source — display source code intermixed with disassembly, if possible. Implies -d.
  • *--prefix=prefix* — specify prefix to add to the absolute paths when used with -S.
  • *--prefix-strip=level* — indicate how many initial directory names to strip off the hardwired absolute paths. It has no effect without --prefix=prefix.
  • --show-raw-insn — when disassembling instructions, print the instruction in hex as well as in symbolic form. This is the default except when --prefix-addresses is used.
  • --no-show-raw-insn — when disassembling instructions, do not print the instruction bytes. This is the default when --prefix-addresses is used.
  • *--insn-width=width* — display width bytes on a single line when disassembling instructions.
  • -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] — displays the contents of the DWARF debug sections in the file, if any are present. Compressed debug sections are automatically decompressed (temporarily) before they're displayed. If one or more of the optional letters or words follows the switch, then only those type(s) of data get dumped. The letters and words refer to:
    • a, =abbrev — displays the contents of the .debug_abbrev section.
    • A, =addr — displays the contents of the .debug_addr section.
    • c, =cu_index — displays the contents of the .debug_cu_index and/or .debug_tu_index sections.
    • f, =frames — display the raw contents of a .debug_frame section.
    • F, =frame-interp — display the interpreted contents of a .debug_frame section.
    • g, =gdb_index — displays the contents of the .gdb_index and/or .debug_names sections.
    • i, =info — displays the contents of the .debug_info section. > Note: the output from this option can also be restricted by the use of the --dwarf-depth and --dwarf-start options.
    • k, =links — displays the contents of the .gnu_debuglink and/or .gnu_debugaltlink sections. Also displays the link to a separate dwarf object file (dwo), if one is specified by the DW_AT_GNU_dwo_name or DW_AT_dwo_name attributes in the .debug_info section.
    • K, =follow-links — display the contents of any selected debug sections found in a linked, separate debug info file. This can result in multiple versions of the same debug section being displayed if both the main file and the separate debug info file contain sections with the same name.

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 too 🫶

⭐ tiny heads-up: in the long-option list up top it's spelled =frames-interp, but the F entry spells it =frame-interp. Copy-paste exactly whichever one your build wants — I don't make the rules 😭

…and the rest of the --debug-dump letters, no cap, here they are:

  • l, =rawline — shows you the contents of the .debug_line section in a raw format (as-is, no interpretation, straight out the box 💅).
  • L, =decodedline — shows you the interpreted contents of the .debug_line section (same section, but translated so it actually reads like something 🫶).
  • m, =macro — dumps the contents of the .debug_macro and/or .debug_macinfo sections.
  • o, =loc — dumps the contents of the .debug_loc and/or .debug_loclists sections.
  • p, =pubnames — dumps the contents of the .debug_pubnames and/or .debug_gnu_pubnames sections.
  • r, =aranges — dumps the contents of the .debug_aranges section.
  • R, =Ranges — dumps the contents of the .debug_ranges and/or .debug_rnglists sections. (Yes, capital R here and capital R in Ranges — it's giving case-sensitive, respect it 🙈)
  • s, =str — dumps the contents of the .debug_str, .debug_line_str and/or .debug_str_offsets sections.
  • t, =pubtype — dumps the contents of the .debug_pubtypes and/or .debug_gnu_pubtypes sections.
  • T, =trace_aranges — dumps the contents of the .trace_aranges section.
  • u, =trace_abbrev — dumps the contents of the .trace_abbrev section.
  • U, =trace_info — dumps the contents of the .trace_info section.
⚠️ Heads up bestie: displaying the contents of .debug_static_funcs, .debug_static_vars and debug_weaknames sections is not currently supported. Not me trying to dump those 💀 — it just won't work.
  • --dwarf-depth=n — limits the dump of the ".debug_info" section to n children. This is only useful with --debug-dump=info. Default vibe is to print all the DIEs; the special value 0 for n will also have this effect (so 0 = no limit, cute).

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 — so it starts counting from 0, periodt.

  • --dwarf-start=n — prints only DIEs beginning with the DIE numbered n. This is only useful with --debug-dump=info.

If you specify it, 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. It's giving "skip to the good part" ✨

This can be used in conjunction with --dwarf-depth — they're besties, they work together 🫶.

  • --dwarf-check — enables additional checks for consistency of Dwarf information. Basically the vibe check for your DWARF data 🔍.
  • -G, --stabs — displays the full contents of any sections requested. Also displays the contents of the .stab and .stab.index and .stab.excl sections from an ELF file. This is only useful on systems (such as Solaris 2.0) in which ".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 — so like, don't come for this flag on Linux, it's just not its moment 🙈.
  • --start-address=address — starts displaying data at the specified address. This affects the output of the -d, -r and -s options. Think of it as your "start here bestie" marker 📍.
  • --stop-address=address — stops displaying data at the specified address. This affects the output of the -d, -r and -s options. The "okay that's enough" marker ✋.
  • -t, --syms — prints 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:
        [  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 auxiliary entries associated with the symbol. The last two fields are the symbol's value and its name. Okay so that's a lot of little fields but honestly they all slay in their own way 💅.

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 referred 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 — those characters are described below, keep scrolling 👀. Next is the section with which the symbol is associated, or *ABS* if the section is absolute (i.e. 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. Iconic lineup, honestly 👑

The flag characters are divided into 7 groups as follows:

  • l, g, u, ! — 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 GNU extension to the standard set of ELF 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. One symbol to rule them all, fr fr.
  • w — the symbol is weak (w) or strong (a space).
  • C — the symbol denotes a constructor (C) or an ordinary symbol (a space).
  • 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. It's literally a little note-to-self in symbol form 🎀.
  • I, 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).
  • d, D — the symbol is a debugging symbol (d) or a dynamic symbol (D) or a normal symbol (a space).
  • F, f, 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).
  • -T, --dynamic-syms — prints 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.

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. Parentheses = "not the default, bestie" 🫶.

  • --special-syms — when displaying symbols, include those which the target considers to be special in some way and which would not normally be of interest to the user. Main character symbols that usually get left out of the group photo 🌟.
  • -V, --version — prints the version number of objdump and exits. Short, sweet, slays, leaves immediately 💨.
  • -x, --all-headers — displays all available header information, including the symbol table and relocation entries. Using -x is equivalent to specifying all of -a -f -h -p -r -t. The "give me everything" option, the full Platte, obsessed 😌.
  • -w, --wide — formats some lines for output devices that have more than 80 columns. Also does not truncate symbol names when they are displayed. If your terminal is wide and you're tired of names getting cut off mid-std::__cxx11::basic_str… — this is your girl 💖.
  • -z, --disassemble-zeroes — normally the disassembly output will skip blocks of zeroes. This option directs the disassembler to disassemble those blocks, just like any other data. Yes bestie, we're looking at the zeroes today. All of them. 🫠
  • @file — read command-line options from file. The options read are inserted in place of the original @file option. If file does not exist, or cannot be read, then the option will be treated literally, and not removed.

Options in file are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The file may itself contain additional @file options; any such options will be processed recursively. It's files all the way down 🌀 — but like, in a cute way.

🔍 SEE ALSO

Go read those too, they're the friend group, iykyk 💜

Copyright (c) 1991-2018 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU 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 "GNU Free Documentation License". (Legal text but make it fashion — it means yes you can share this, just keep the license with it 🎀)

✨ and that's the whole page bestie ✨ This masterpiece is from binutils-2.30, dated 2018-01-27, and it's the OBJDUMP(1) manual — go forth and dump responsibly, mwah 💋🦋

📦 where this page comes from