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. Not DWARF
link will take place.
- -f, --flat
- 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.
- --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.
- -j <n>,
--num-threads=<n>
- Specifies the maximum number (n) of simultaneous threads to use
when linking multiple architectures.
- -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.
- -s, --symtab
- Dumps the symbol table found in executable or object file(s) and
exits.
- -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 (http://llvm.org/).