DSYMUTIL(1)

📦
version 14.0.6 · 8 versions
, in ubuntu questing

💖 DSYMUTIL(1) 💖

okay bestie, pull up a chair, because we're about to talk about dsymutil — that's the LLVM tool that manipulates archived DWARF debug symbol files. yes. that's the whole vibe. it's giving "quiet little utility that carries your entire debugging experience on its back" and honestly? we're obsessed. ✨

🌸 NAME 🌸

dsymutil — manipulate archived DWARF debug symbol files 🦋

✨ SYNOPSIS ✨

dsymutil [options] executable

💅 DESCRIPTION 💅

So here's the tea, bestie. dsymutil links the DWARF debug information that lives inside the object files for an executable, and it does this by using the debug symbols info chillin' in that executable's symbol table. Like, it's literally matchmaking object files with their debug data. 🫶

By default — no cap — the linked debug information gets dropped into a .dSYM bundle with the exact same name as the executable. That's just the default. It's the moment. 👑

🎀 OPTIONS 🎀

  • --accelerator=<accelerator type> — Pick which type of accelerator table you want. The valid options are Apple, Dwarf and Default. That's it, that's the list, don't get creative. ⭐
  • --arch <arch> — Only link DWARF debug info for the CPU architecture types you name here. Architectures can be specified by name. Heads up though: when you use this option, if any architectures can't be properly linked, you get an error back. You can pass this option multiple times — once per desired architecture. By default all CPU architectures get linked, and any that can't be properly linked will make dsymutil return an error. 😭
  • --dump-debug-map — Dumps the executable's debug-map (that's the list of object files holding the debug info) in YAML format and then dips out. No DWARF link happens at all. just a lil peek. 🙈
  • --flat, -f — Produce a flat dSYM file. A .dwarf extension gets appended to the executable name unless you specify the output file with the -o option. flat. no bundle. streamlined. 💅
  • --gen-reproducer — Generate a reproducer made up of the input object files. for when you need receipts. 🧚
  • --help, -h — Print this help output. the classic. the icon. 🎀
  • --keep-function-for-static — Makes a static variable keep the enclosing function, even if that function would've been omitted otherwise. protective energy fr fr. 🫶
  • --minimize, -z — When you use this while creating a dSYM file, it suppresses the emission of the .debug_inlines, .debug_pubnames, and .debug_pubtypes sections, since dsymutil currently has better equivalents: .apple_names and .apple_types. And when you use it together with the --update option, it'll cause redundant accelerator tables to be removed. spring cleaning, but for your debug sections. ✨
  • --no-odr — Do not use ODR (One Definition Rule) for uniquing C++ types. simple as that. 🌸
  • --no-output — Do the link in memory, but do not emit the result file. all the work, none of the output. it's giving ghosting (affectionate). 👻
  • --no-swiftmodule-timestamp — Don't check the timestamp for swiftmodule files. timestamps? not today. 💜
  • --num-threads <threads>, -j <threads> — Specifies the maximum number (n) of simultaneous threads to use when linking multiple architectures. parallelize, bestie. 🔥
  • --object-prefix-map <prefix=remapped> — Remap object file paths (but no source paths) before processing. Use this for Clang objects where the module cache location was remapped using -fdebug-prefix-map; it helps dsymutil find the Clang module cache. iykyk. 🦋
  • --oso-prepend-path <path> — Specifies a path to prepend to all debug symbol object file paths. 🍓
  • --out <filename>, -o <filename> — Specifies an alternate path to place the dSYM bundle. The default dSYM bundle path is created by appending .dSYM to the executable name. 🎀
  • --papertrail — When you're running dsymutil as part of your build system, it can be desirable for warnings to be part of the end product instead of just being emitted to the output stream. When enabled, warnings are embedded in the linked DWARF debug information. leaving a lil trail. iconic behavior. ⭐
  • --remarks-output-format <format> — Specify the format to be used when serializing the linked remarks. 💅
  • --remarks-prepend-path <path> — Specify a directory to prepend the paths of the external remark files. 🌈
  • --statistics — Print statistics about the contribution of each object file to the linked debug info. This prints a table after linking with the object file name, the size of the debug info in the object file (in bytes) and the size contributed (in bytes) to the linked dSYM. The table is sorted by the output size, listing the object files with the largest contribution first. leaderboard energy. 👑
  • --symbol-map <bcsymbolmap> — Update the existing dSYMs inplace using the symbol map specified. inplace. no copies. 💜
  • -s, --symtab — Dumps the symbol table found in executable or object file(s) and exits. 🦋
  • -S — Output textual assembly instead of a binary dSYM companion file. going full text mode. ✨
  • --toolchain <toolchain> — Embed the toolchain in the dSYM bundle's property list. 🌸
  • -u, --update — Update an existing dSYM file to contain the latest accelerator tables and other DWARF optimizations. This option will rebuild the .apple_names and .apple_types hashed accelerator tables. glow-up for your dSYM. 💅
  • --use-reproducer <path> — Use the object files from the given reproducer path. 🧚
  • --verbose — Display verbose information when linking. tell me everything, bestie. 💖
  • --verify — Run the DWARF verifier on the linked DWARF debug info. vibe check on your debug info. ✅
  • -v, --version — Display the version of the tool. 🎀
  • -y — Treat executable as a YAML debug-map rather than an executable. plot twist. 🙈

🫶 EXIT STATUS 🫶

dsymutil returns 0 if the DWARF debug information was linked successfully. Otherwise, it returns 1. That's the whole scoring system. no cap. 😭

👀 SEE ALSO 👀

llvm-dwarfdump(1)

💜 AUTHOR 💜

Maintained by the LLVM Team (https://llvm.org/). we love a maintainer who shows up. 🫶

2003-2025, LLVM Project

ok and that's the whole page bestie!! this one's from LLVM, page 14 of the manual, dated 2025-05-22 — so if you're reading this on some random Tuesday, just know that this page has been out here slaying since May 22, 2025. DSYMUTIL(1) forever. periodt. 💅✨🦋
📦 where this page comes from