READELF(1)

🎀 readelf(1) — GNU Development Tools 🎀

okay bestie, this is the manual page for readelf, from GNU Development Tools, and it’s lowkey the tool you want when you need to peek inside ELF files without getting tangled up in BFD. it’s giving main-character energy for object-file inspection, no cap. 💅✨

✨ NAME ✨

readelf — display information about ELF files. that’s the whole vibe: it shows you what’s inside ELF object files. 🦋

🦋 SYNOPSIS 🦋

the full command shape is here, bestie — every flag exactly where it belongs:

readelf [-a|--all]
        [-h|--file-header]
        [-l|--program-headers|--segments]
        [-S|--section-headers|--sections]
        [-g|--section-groups]
        [-t|--section-details]
        [-e|--headers]
        [-s|--syms|--symbols]
        [--dyn-syms|--lto-syms]
        [--sym-base=[0|8|10|16]]
        [--demangle=style|--no-demangle]
        [--quiet]
        [--recurse-limit|--no-recurse-limit]
        [-U method|--unicode=method]
        [-X|--extra-sym-info|--no-extra-sym-info]
        [-n|--notes]
        [-r|--relocs]
        [-u|--unwind]
        [-d|--dynamic]
        [-V|--version-info]
        [-A|--arch-specific]
        [-D|--use-dynamic]
        [-L|--lint|--enable-checks]
        [-x <number or name>|--hex-dump=<number or name>]
        [-p <number or name>|--string-dump=<number or name>]
        [-R <number or name>|--relocated-dump=<number or name>]
        [-j <number or name>|--display-section=<number or name>]
        [-z|--decompress]
        [-c|--archive-index]
        [-w|--debug-dump]
        [-wa|--debug-dump=abbrev]
        [-wA|--debug-dump=addr]
        [-wr|--debug-dump=aranges]
        [-wc|--debug-dump=cu_index]
        [-wL|--debug-dump=decodedline]
        [-wf|--debug-dump=frames]
        [-wF|--debug-dump=frames-interp]
        [-wg|--debug-dump=gdb_index]
        [-wi|--debug-dump=info]
        [-wk|--debug-dump=links]
        [-wo|--debug-dump=loc]
        [-wm|--debug-dump=macro]
        [-wp|--debug-dump=pubnames]
        [-wt|--debug-dump=pubtypes]
        [-wR|--debug-dump=Ranges]
        [-wl|--debug-dump=rawline]
        [-ws|--debug-dump=str]
        [-wO|--debug-dump=str-offsets]
        [-wu|--debug-dump=trace_abbrev]
        [-wT|--debug-dump=trace_aranges]
        [-wU|--debug-dump=trace_info]
        [-wK|--debug-dump=follow-links]
        [-wN|--debug-dump=no-follow-links]
        [-wD|--debug-dump=use-debuginfod]
        [-wE|--debug-dump=do-not-use-debuginfod]
        [--debug-dir=dir]
        [-P|--process-links]
        [--dwarf-depth=n]
        [--dwarf-start=n]
        [--ctf=section]
        [--ctf-parent=section]
        [--ctf-symbols=section]
        [--ctf-strings=section]
        [--sframe=section]
        [-I|--histogram]
        [--got-contents]
        [-v|--version]
        [-W|--wide]
        [-T|--silent-truncation]
        [-H|--help]
        elffile...

💖 DESCRIPTION 💖

readelf displays information about one or more ELF format object files. the options control what particular information to display. 🫶

elffile... are the object files to be examined. 32-bit and 64-bit ELF files are supported, as are archives containing ELF files. so yes, bestie, it handles both sizes and archives too. 🌸

this program performs a similar function to objdump, but it goes into more detail and it exists independently of the BFD library. so if there is a bug in BFD then readelf will not be affected. iconic separation, honestly. 👑

👑 OPTIONS 👑

the long and short forms of options, shown here as alternatives, are equivalent. at least one option besides -v or -H must be given. ⭐

• -a, --all — equivalent to specifying --file-header, --program-headers, --sections, --symbols, --relocs, --dynamic, --notes, --got-contents, --version-info, --arch-specific, --unwind, --section-groups and --histogram.

note: this option does not enable --use-dynamic itself, so if that option is not present on the command line then dynamic symbols and dynamic relocs will not be displayed. 💅

• -h, --file-header — displays the information contained in the ELF header at the start of the file. 🎀
• -l, --program-headers, --segments — displays the information contained in the file’s segment headers, if it has any. 🦋
• --quiet — suppress the "no symbols" diagnostic. shhh, bestie. 🙈
• -S, --sections, --section-headers — displays the information contained in the file’s section headers, if it has any. 🌸
• -g, --section-groups — displays the information contained in the file’s section groups, if it has any. 💜
• -t, --section-details — displays the detailed section information. implies -S. 🔥
• -s, --symbols, --syms — displays the entries in the symbol table section of the file, if it has one. if a symbol has version information associated with it then this is displayed as well. the version string is displayed as a suffix to the symbol name, preceded by an @ character. for example foo@VER_1. if the version is the default version to be used when resolving unversioned references to the symbol then it is displayed as a suffix preceded by two @ characters. for example foo@@VER_2. 🫶
• --dyn-syms — displays the entries in the dynamic symbol table section of the file, if it has one. the output format is the same as the format used by the --syms option. ✨
• --lto-syms — displays the contents of any LTO symbol tables in the file. 🧚
• --sym-base=[0|8|10|16] — forces the size field of the symbol table to use the given base. any unrecognized options will be treated as 0. --sym-base=0 represents the default and legacy behaviour. this will output sizes as decimal for numbers less than 100000. for sizes 100000 and greater hexadecimal notation will be used with a 0x prefix. --sym-base=8 will give the symbol sizes in octal. --sym-base=10 will always give the symbol sizes in decimal. --sym-base=16 will always give the symbol sizes in hexadecimal with a 0x prefix. 💀
• -C, --demangle[=style] — decode (demangle) low-level symbol names into user-level names. 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. 🌈
• --no-demangle — do not demangle low-level symbol names. this is the default. 🍓
• --recurse-limit, --no-recurse-limit, --recursion-limit, --no-recursion-limit — enables or disables a limit on the amount of recursion performed whilst demangling strings. since the name mangling formats allow for an infinite level of recursion it is possible to create strings whose decoding will exhaust the amount of stack space available on the host machine, triggering a memory fault. the limit tries to prevent this from happening by restricting recursion to 2048 levels of nesting.

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. 😭 dramatic but true.

• -U [d|i|l|e|x|h], --unicode=[default|invalid|locale|escape|hex|highlight] — controls the display of non-ASCII characters in identifier names. the default (--unicode=locale or --unicode=default) is to treat them as multibyte characters and display them in the current locale. all other versions of this option treat the bytes as UTF-8 encoded values and attempt to interpret them. if they cannot be interpreted or if the --unicode=invalid option is used then they are displayed as a sequence of hex bytes, enclosed in curly parenthesis characters.

using the --unicode=escape option will display the characters as unicode escape sequences (\uxxxx). using the --unicode=hex will display the characters as hex byte sequences enclosed between angle brackets.

using the --unicode=highlight will display the characters as unicode escape sequences but it will also highlight them in red, assuming that colouring is supported by the output device. the colouring is intended to draw attention to the presence of unicode sequences when they might not be expected. 🌸

• -X, --extra-sym-info — when displaying details of symbols, include extra information not normally presented. currently this just adds the name of the section referenced by the symbol’s index field, if there is one. in the future more information may be displayed when this option is enabled.

enabling this option effectively enables the --wide option as well, at least when displaying symbol information. 🔥

• --no-extra-sym-info — disables the effect of the --extra-sym-info option. this is the default. 🎀
• -e, --headers — display all the headers in the file. equivalent to -h -l -S. ✨
• -n, --notes — displays the contents of the NOTE segments and/or sections, if any. 📝
• -r, --relocs — displays the contents of the file’s relocation section, if it has one. 💜
• -u, --unwind — displays the contents of the file’s unwind section, if it has one. only the unwind sections for IA64 ELF files, as well as ARM unwind tables (".ARM.exidx" / ".ARM.extab") are currently supported. if support is not yet implemented for your architecture you could try dumping the contents of the .eh_frames section using the --debug-dump=frames or --debug-dump=frames-interp options. 🦋
• -d, --dynamic — displays the contents of the file’s dynamic section, if it has one. 🌈
• -V, --version-info — displays the contents of the version sections in the file, if they exist. ⭐
• -A, --arch-specific — displays architecture-specific information in the file, if there is any. 🧚
• -D, --use-dynamic — when displaying symbols, this option makes readelf use the symbol hash tables in the file’s dynamic section, rather than the symbol table sections.

when displaying relocations, this option makes readelf display the dynamic relocations rather than the static relocations. 💅

• -L, --lint, --enable-checks — displays warning messages about possible problems with the file(s) being examined. if used on its own then all of the contents of the file(s) will be examined. if used with one of the dumping options then the warning messages will only be produced for the things being displayed. 👑
• -x <number or name><br>--hex-dump=<number or name> — okay so this one dumps the contents of the section you point at as hexadecimal bytes 🧚 A number picks a specific section by its index in the section table, and literally any other string picks all sections with that name in the object file. And the glow-up? You can repeat this option multiple times on the command line to request multiple hex dumps 💅
• -R <number or name><br>--relocated-dump=<number or name> — same energy as above, displays the indicated section as hexadecimal bytes, except the contents get relocated before they're shown ✨ Same deal with the number vs. name thing: number = section by index in the section table, any other string = all sections with that name in the object file. Repeatable as many times as you want for multiple relocated dumps 🎀
• -p <number or name><br>--string-dump=<number or name> — this one shows the indicated section's contents as printable strings 🍓 Again, number = a particular section by index in the section table, any other string = all sections with that name in the object file. And yes bestie, repeatable multiple times for multiple string dumps 💖
• -j <number or name><br>--display-section — the main character option that just gets it 👑 It displays the indicated section's contents according to its section header type. Sections containing relocations get displayed as if --relocations had been used, sections containing symbols get displayed as if --syms had been used, and so on — it literally reads the room and matches the vibe 🦋

A number identifies a particular section by index in the section table; any other string identifies all sections with that name in the input file(s).

Repeatable multiple times on the command line for multiple section dumps, obviously 💅

• -z<br>--decompress — politely requests that the section(s) being dumped by the x, R or p options get decompressed before being displayed ✨ And if they aren't compressed in the first place? They just get displayed as is, no drama 🎀
• -c<br>--archive-index — displays the file symbol index information living in the header part of binary archives 📚 Does the exact same thing as the t command to ar, but without using the BFD library. iykyk 😌
• -w[lLiaprmfFsOoRtUuTgAckK]<br>--debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=str-offsets,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links] — the big one 💀 Displays the contents of the DWARF debug sections in the file, if any are present. Compressed debug sections get automatically decompressed (temporarily) before they're displayed. And 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" — displays the raw contents of a .debug_frame section.
  • "F", "=frames-interp" — displays 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 --dwarf-depth and --dwarf-start options.
  • "k", "=links" — displays the contents of the .gnu_debuglink, .gnu_debugaltlink and .debug_sup sections, if any of them are present. Also displays any links to separate dwarf object files (dwo), if they're specified by the DW_AT_GNU_dwo_name or DW_AT_dwo_name attributes in the .debug_info section.
  • "K", "=follow-links" — displays the contents of any selected debug sections found in linked, separate debug info file(s). Heads up: this can result in multiple versions of the same debug section being displayed if it exists in more than one file 🙈

In addition, when displaying DWARF attributes, if a form is found that references the separate debug info file, then the referenced contents also get displayed.

Note — in some distributions this option is enabled by default. It can be disabled via the N debug option. The default can be chosen when configuring the binutils via the --enable-follow-debug-links=yes or --enable-follow-debug-links=no options. If these aren't used, then the default is to enable the following of debug links ✨

Note — if support for the debuginfod protocol was enabled when the binutils were built, then this option will also include an attempt to contact any debuginfod servers mentioned in the DEBUGINFOD_URLS environment variable. This could take some time to resolve 😭 This behaviour can be disabled via the =do-not-use-debuginfod debug option.

• "N", "=no-follow-links" — disables the following of links to separate debug info files 🚫
• "D", "=use-debuginfod" — enables contacting debuginfod servers if there's a need to follow debug links. This is the default behaviour 💖
• "E", "=do-not-use-debuginfod" — disables contacting debuginfod servers when there's a need to follow debug links.
• "l", "=rawline" — displays the contents of the .debug_line section in a raw format.
• "L", "=decodedline" — displays the interpreted contents of the .debug_line section.
• "m", "=macro" — displays the contents of the .debug_macro and/or .debug_macinfo sections.
• "o", "=loc" — displays the contents of the .debug_loc and/or .debug_loclists sections.
• "O", "=str-offsets" — displays the contents of the .debug_str_offsets section.
• "p", "=pubnames" — displays the contents of the .debug_pubnames and/or .debug_gnu_pubnames sections.
• "r", "=aranges" — displays the contents of the .debug_aranges section.
• "R", "=Ranges" — displays the contents of the .debug_ranges and/or .debug_rnglists sections.
• "s", "=str" — displays the contents of the .debug_str, .debug_line_str and/or .debug_str_offsets sections.
• "t", "=pubtype" — displays the contents of the .debug_pubtypes and/or .debug_gnu_pubtypes sections.
• "T", "=trace_aranges" — displays the contents of the .trace_aranges section.
• "u", "=trace_abbrev" — displays the contents of the .trace_abbrev section.
• "U", "=trace_info" — displays the contents of the .trace_info section.

Note: displaying the contents of .debug_static_funcs, .debug_static_vars and debug_weaknames sections is not currently supported 😔 Don't come for me, I don't make the rules.

• --dwarf-depth=n — limits the dump of the ".debug_info" section to n children 🌸 Only useful with --debug-dump=info. The default is to print all DIEs, and 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, bestie 🎀

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

If specified, this option suppresses printing of any header information and all DIEs before the DIE numbered n. Only siblings and children of the specified DIE get printed.

This can be used in conjunction with --dwarf-depth — they're literally besties 🫶

• --debug-dir=dir — search dir when looking for separate debug info files 🔍
• -P<br>--process-links — displays the contents of non-debug sections found in separate debuginfo files that are linked to the main file. This option automatically implies the -wK option, and only sections requested by other command line options get displayed ✨
• --ctf[=section] — displays the contents of the specified CTF section. CTF sections themselves contain many subsections, all of which are displayed in order 🦋

By default, it displays the name of the section named .ctf, which is the name emitted by ld.

• --ctf-parent=member — so if the CTF section contains ambiguously-defined types, it'll consist of an archive of many CTF dictionaries, all inheriting from one dictionary containing unambiguous types. This member is by default named .ctf, like the section containing it, but it's possible to change this name using the "ctf_link_set_memb_name_changer" function at link time 👑 When looking at CTF archives that were created by a linker that uses the name changer to rename the parent archive member, --ctf-parent can be used to specify the name used for the parent 💅
• --ctf-parent-section=section — this option lets you pick a completely different section for the CTF parent dictionary containing unambiguous types than for the child dictionaries that contain the ambiguous remainder 🌈 The linker does not emit ELF objects structured like this, but some third-party linkers may. It's also convenient to inspect CTF written out as multiple raw files to compose them with objcopy, which can put them in different ELF sections but not in different members of a single CTF dict 💀
• --ctf-symbols=section<br>--ctf-strings=section — specify the name of another section from which the CTF file can inherit strings and symbols 🍓 By default, the ".symtab" and its linked string table are used.

Careful bestie: if either --ctf-symbols or --ctf-strings is specified, the other must be specified as well. No solo acts 😤

• --got-contents — displays the contents of the file's Global Offset Table (GOT) sections, if it has any 💖 For MIPS, this option is similar to --arch-specific, but it only displays the GOT-related contents and it's ignored when --arch-specific is used.
• -I<br>--histogram — displays a histogram of bucket list lengths when displaying the contents of the symbol tables 📊 Slay, stats.
• -v, --version — bestie just wants to know who she is 💅 prints out the version number of readelf, that's it, that's the whole vibe.
• -W, --wide — okay so by default readelf is out here doing the most, breaking section header lines and segment listing lines for 64-bit ELF files so everything squeezes into 80 columns 😭 this flag says "not today" and stops the line-breaking. Now each section header (resp. each segment) gets printed on a single line, which is so much more readable on terminals wider than 80 columns. wide-screen queen behavior 👑
• -T, --silent-truncation — so normally when readelf is showing a symbol name and it has to truncate it to fit into an 80 column display, it adds a suffix of [...] to the name. This command line option disables that whole behavior, which means you get 5 more characters of the name to be displayed, and it restores the old readelf behavior from prior to release 2.35. retro revival fr fr 🫶
• -H, --help — displays all the command-line options that readelf understands. the little "what can u even do" menu ✨
• @file — reads command-line options from file. The options that get read are inserted in place of the original @file option. And listen: if file does not exist, or it can't be read, then the option gets treated literally and is not removed 💀 (so it just sits there, awkward).

Options inside file are separated by whitespace. A whitespace character can be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) can be included by prefixing the character to be included with a backslash. And plot twist — the file may itself contain additional @file options, and any such options get processed recursively 🌀 it's giving inception, it's giving turtles all the way down.

---

💫 SEE ALSO 💫

• objdump(1) — her chaotic sibling 🫶
• and the Info entries for binutils, which is where the real lore lives 📚

---

📜 COPYRIGHT 📜

Copyright (c) 1991-2026 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".

bestie this is the legal bit so read it properly, no skimming 🙈 it's literally permission to copy, distribute and/or modify this document, but the conditions above are the whole deal, okay?

---

and that's the whole page, you made it to the end!! 🎀 this was binutils-2.47, dated 2026-08-26, filed under READELF(1) — go read some ELF headers, you absolute icon, i'm obsessed 💖✨🦋