DSYMUTIL(1)

💖 DSYMUTIL(1) 💖

okay so bestie, welcome to the dsymutil page — that's section 1 of the LLVM manual, and yes she is that girl. grab a boba, we're linking debug info 🧋✨

---

✨ NAME ✨

dsymutil — manipulate archived DWARF debug symbol files 🦋

---

🌸 SYNOPSIS 🌸

dsymutil [options] executable

---

💅 DESCRIPTION 💅

So here's the vibe: dsymutil links up the DWARF debug information that lives inside the object files for an executable called executable, and it does that by using the debug symbol info sitting in its symbol table. 🔍

By default, the linked debug info gets dropped into a .dSYM bundle with the same name as the executable. iconic behaviour honestly 💖

---

🎀 OPTIONS 🎀

• --accelerator=<accelerator type> — pick which kind of accelerator table you want. the valid options are 'Apple', 'Dwarf', 'Default' and 'None'. choose your fighter ✨
• --arch <arch> — only link DWARF debug info for the CPU architecture types you name here. architectures can be specified by name. if you use this option and any architecture can't be properly linked, you get an error. you can pass this option multiple times — once for each architecture you want. by default all CPU architectures get linked, and any that can't be properly linked will make dsymutil return an error. no skipping, bestie 😤
• --build-variant-suffix <suffix=buildvariant> — specify the build variant suffix used to build the executable file. a product's binary can have multiple variants, each built slightly differently. the most common build variants are 'debug' and 'profile'. setting the DYLD_IMAGE_SUFFIX environment variable will make dyld load the specified variant at runtime. 🧚
• --dump-debug-map — dump the executable's debug-map (that's the list of object files that contain the debug information) in YAML format and exit. no DWARF link will take place. just a lil peek, no commitment 🙈
  • -D <path> — specify a directory that contain dSYM files to search for. this is used for mergeable libraries, so dsymutil knows where to look for dSYM files with debug information about symbols present in those libraries. (yes, she's tucked under --dump-debug-map in the original — we keep her right where she was 💜)
• --fat64 — use a 64-bit header when emitting universal binaries. thicc header energy 👑
• --flat, -f — produce a flat dSYM file. a .dwarf extension will be appended to the executable name unless the output file is specified using the -o option. flatten it, slay 💅
• --gen-reproducer — generate a reproducer consisting of the input object files. alias for --reproducer=GenerateOnExit. ✨
• --help, -h — print this help output. hi bestie 👋
• --keep-function-for-static — make a static variable keep the enclosing function even if it would have been omitted otherwise. don't let the function go, it's giving loyalty 🫶
• --minimize, -z — when used when creating a dSYM file, this option will suppress the emission of the .debug_inlines, .debug_pubnames, and .debug_pubtypes sections, since dsymutil currently has better equivalents: .apple_names and .apple_types. when used in conjunction with the --update option, this option will cause redundant accelerator tables to be removed. declutter queen 🧹
• --no-object-timestamp — don't check timestamp for object files. ⏰🚫
• --no-odr — do not use ODR (One Definition Rule) for uniquing C++ types. 😭
• --no-output — do the link in memory, but do not emit the result file. all vibes, no artifact 💀
• --no-swiftmodule-timestamp — don't check the timestamp for swiftmodule files. 🦋
• --num-threads <threads>, -j <threads> — specifies the maximum number (n) of simultaneous threads to use when linking multiple architectures. multitasking main character 🔥
• --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. 🗺️
• --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. pick your own adventure 💖
• -q, --quiet — enable quiet mode and limit output. shhh, she's resting 🤫
• --remarks-drop-without-debug — drop remarks without valid debug locations. without this flags, all remarks are kept. (that's the original's wording, bestie, we don't touch it ✨)
• --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. 🍓
• --reproducer <mode> — specify the reproducer generation mode. valid options are 'GenerateOnExit', 'GenerateOnCrash', 'Use', 'Off'. ⭐
• --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. numbers girlie 📊✨
• -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. 🧚
• --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 in progress 💅
• --use-reproducer <path> — use the object files from the given reproducer path. alias for --reproducer=Use. 🔁
• --verbose — display verbose information when linking. she's telling you everything 🗣️
• --verify — run the DWARF verifier on the linked DWARF debug info. vibe check on your debug info fr fr ✅
• -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. so basically: 0 = ate, 1 = did not eat 😭

---

🌈 SEE ALSO 🌈

llvm-dwarfdump(1)

---

👑 AUTHOR 👑

Maintained by the LLVM Team (https://llvm.org/). 💖

---

💀 COPYRIGHT 💀

2003-2025, LLVM Project

---

and that's the whole page bestie!! this was LLVM version 20, dated 2025-09-03, and it's the DSYMUTIL(1) manual — periodt 💅✨🦋 no cap, go link some debug info 🫶