dsymutil - manipulate archived DWARF debug symbol files
dsymutil [options] executable
dsymutil links the DWARF debug information found in the
object files for an executable executable by using debug symbols
information contained in its symbol table. By default, the linked debug
information is placed in a .dSYM bundle with the same name as the
executable.
- --arch
<arch>
- Link DWARF debug information only for specified CPU architecture types.
Architectures may be specified by name. When using this option, an error
will be returned if any architectures can not be properly linked. This
option can be specified multiple times, once for each desired
architecture. All CPU architectures will be linked by default and any
architectures that can't be properly linked will cause dsymutil to
return an error.
- --dump-debug-map
- Dump the executable's debug-map (the list of the object files
containing the debug information) in YAML format and exit. No DWARF link
will take place.
- --fat64
- Use a 64-bit header when emitting universal binaries.
- --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.
- --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 --update option, this
option will cause redundant accelerator tables to be removed.
- --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.
- --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; to help dsymutil find the Clang module
cache.
- --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 running dsymutil as part of your build system, it can be desirable
for warnings to be part of the end product, rather than just being emitted
to the output stream. When enabled warnings are embedded in the linked
DWARF debug information.
- Drop remarks without valid debug locations. Without this flags, all
remarks are kept.
- Specify the format to be used when serializing the linked remarks.
- 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.
- -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.
- -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.
- --verbose
- Display verbose information when linking.
- --verify
- Run the DWARF verifier on the linked DWARF debug info.
- -y
- Treat executable as a YAML debug-map rather than an
executable.
dsymutil returns 0 if the DWARF debug information was
linked successfully. Otherwise, it returns 1.
Maintained by the LLVM Team (https://llvm.org/).