LLVM-DWARFDUMP(1)

πŸ’… LLVM-DWARFDUMP(1) β€” bestie's guide to the LLVM manual ✨

okay so this is llvm-dwarfdump, a page from the LLVM manual, and it's literally the tool you call when you want to see what's actually inside your DWARF debug info. let's get into it 🫢


🌸 NAME 🌸

llvm-dwarfdump β€” dump and verify DWARF debug information. that's the whole vibe. πŸ’–


✨ SYNOPSIS ✨

llvm-dwarfdump [options] [filename ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so llvm-dwarfdump parses the DWARF sections inside object files, archives, and .dSYM bundles, and then prints the contents in human-readable form. it's giving translator, honestly πŸ’…

here's the important part though: only the .debug_info section gets printed unless you specifically ask for one of the section-specific options, or you hit it with --all. so don't come for it when you only see .debug_info β€” that's the default, bestie.

and if you don't give it any input file at all? it just uses a.out instead. iconic default behavior ✨ and if you pass - as the input file, llvm-dwarfdump reads the input from its standard input stream. very cat-core of it.


πŸŽ€ OPTIONS πŸŽ€

  • -a, --all β€” dump all supported DWARF sections. all of them. every single one. periodt.
  • --arch=<arch> β€” dump DWARF debug information for the specified CPU architecture. you can name the architecture by name or by number, and you can pass this option multiple times β€” once for each architecture you want. by default, all CPU architectures will be printed.
  • -c, --show-children β€” show a debug info entry's children when you're selectively printing with the =<offset> argument of --debug-info, or with options like --find or --name. the kids are coming too πŸ’€
  • --color β€” use colors in output. slay 🌈
  • --error-display=<value> β€” sets how much detail and summary you get when verifying. implies --verify. the supported values are:
    • quiet β€” only display whether errors occurred.
    • summary β€” display only a summary of the errors found.
    • details β€” display each error in detail but no summary.
    • full β€” display each error as well as a summary. [default]
  • -f <name>, --find=<name> β€” search for the exact text <name> in the accelerator tables and print the matching debug information entries. when there are no accelerator tables, or the name of the DIE you're looking for isn't in the accelerator tables, try the slower but more complete --name option. she's thorough but she's not fast, iykyk 😭
  • -F, --show-form β€” show DWARF form types after the DWARF attribute types. little bonus info, we love ✨
  • -h, --help β€” show help and usage for this command.
  • --help-list β€” show help and usage for this command without grouping the options into categories. ungrouped. unbothered. πŸ’…
  • -i, --ignore-case β€” ignore case distinctions when using --name.
  • -n <name>, --name=<name> β€” find and print all debug info entries whose name (the DW_AT_name attribute) is <name>. yes, all of them.
  • --lookup=<address> β€” look up <address> in the debug information and print out the file, function, block, and line table details. the full backstory fr fr
  • -o <path> β€” redirect output to a file specified by <path>, where - is the standard output stream.
  • -p, --show-parents β€” show a debug info entry's parents when selectively printing with the =<offset> argument of --debug-info, or options like --find or --name. family tree reveal 🧚
  • --parent-recurse-depth=<N> β€” when displaying debug info entry parents, only show them to a maximum depth of <N>. we're not going all the way back to the ancestors.
  • --quiet β€” use with --verify to not emit to STDOUT. shhh 🀫
  • -r <N>, --recurse-depth=<N> β€” when displaying debug info entries, only show children to a maximum depth of <N>.
  • --show-section-sizes β€” show the sizes of all debug sections, expressed in bytes.
  • --show-sources β€” print all source files mentioned in the debug information. absolute paths are given whenever possible.
  • --statistics β€” collect debug info quality metrics and print the results as machine-readable single-line JSON output. the output format is described below in the section FORMAT OF STATISTICS OUTPUT. πŸ“
  • --summarize-types β€” abbreviate the description of type unit entries. less reading, same energy.
  • -x, --regex β€” treat any <name> strings as regular expressions when searching with --name. and if --ignore-case is also specified, the regular expression becomes case-insensitive. regex girlies rise πŸ‘‘
  • -u, --uuid β€” show the UUID for each architecture.
  • --diff β€” dump the output in a format that is more friendly for comparing DWARF output from two different files.
  • -v, --verbose β€” display verbose information when dumping. this can help to debug DWARF issues. when things are weird, go verbose, ngl.
  • --verify β€” verify the structure of the DWARF information by verifying the compile unit chains, DIE relationships graph, address ranges, and more. the vibe check of debug info πŸ’€
  • --verify-json=<path> β€” output JSON-formatted error summary to the file specified by <path>. implies --verify. the output format is described below in the section FORMAT OF VERIFY JSON OUTPUT.
  • --version β€” display the version of the tool.
  • --debug-abbrev, --debug-addr, --debug-aranges, --debug-cu-index, --debug-frame [=<offset>], --debug-gnu-pubnames, --debug-gnu-pubtypes, --debug-info [=<offset>], --debug-line [=<offset>], --debug-line-str, --debug-loc [=<offset>], --debug-loclists [=<offset>], --debug-macro, --debug-names, --debug-pubnames, --debug-pubtypes, --debug-ranges, --debug-rnglists, --debug-str, --debug-str-offsets, --debug-tu-index, --debug-types [=<offset>], --eh-frame [=<offset>], --gdb-index, --apple-names, --apple-types, --apple-namespaces, --apple-objc β€” dump the specified DWARF section by name. only the .debug_info section is shown by default. some entries support adding an =<offset> as a way to provide an optional offset of the exact entry to dump within the respective section. when an offset is provided, only the entry at that offset will be dumped; otherwise the entire section will be dumped.
    • heads up: the --debug-macro option prints both the .debug_macro and the .debug_macinfo sections. two for one πŸ’–
    • also, --debug-frame and --eh-frame are aliases β€” in cases where both sections are present, one command outputs both.
  • @<FILE> β€” read command-line options from <FILE>. cute lil options file πŸŽ€

🧚 FORMAT OF STATISTICS OUTPUT 🧚

the --statistics option generates single-line JSON output representing quality metrics of the processed debug info. these metrics are useful to compare changes between two compilers β€” particularly for judging the effect that a change to the compiler has on the debug info quality. like a report card for your compiler, honestly πŸ“

the output is formatted as key-value pairs. the first pair contains a version number. the following naming scheme is used for the keys:

  • variables ==> local variables and parameters
  • local vars ==> local variables
  • params ==> formal parameters

for aggregated values, the following keys are used:

  • sum_of_all_variables(...) ==> the sum applied to all variables
  • #bytes ==> the number of bytes
  • #variables - entry values ... ==> the number of variables excluding the entry values etc.

πŸ”₯ FORMAT OF VERIFY JSON OUTPUT πŸ”₯

the format of the JSON output created by the --verify-json is:

{
  "error-categories": {
    "<first category description>": {"count": 1234},
    "<next category description>": {"count": 4321}
  },
  "error-count": 5555
}

the following is generated if there are no errors reported:

{
  "error-categories": {},
  "error-count": 0
}

no errors? no categories. zero error-count. we love a clean run ✨


⭐ EXIT STATUS ⭐

llvm-dwarfdump returns 0 if the input files were parsed and dumped successfully. otherwise, it returns 1. simple as that, bestie.


🌈 SEE ALSO 🌈

dsymutil(1) β€” <dsymutil.html>


πŸ’œ Author πŸ’œ

maintained by the LLVM Team (https://llvm.org/). they're the main characters of this story, fr fr πŸ‘‘

2003-2026, LLVM Project


and that's the whole page, no cap πŸ’… this was LLVM-DWARFDUMP(1) from the LLVM manual, dated 2026-05-15 β€” go dump some DWARF, you absolute icon πŸ¦‹πŸ’–
πŸ“¦ where this page comes from