1DSYMUTIL(1)                          LLVM                          DSYMUTIL(1)
2
3
4

NAME

6       dsymutil - manipulate archived DWARF debug symbol files
7

SYNOPSIS

9       dsymutil [options] executable
10
11

DESCRIPTION

13       dsymutil  links  the  DWARF debug information found in the object files
14       for an executable executable by using debug  symbols  information  con‐
15       tained in its symbol table. By default, the linked debug information is
16       placed in a .dSYM bundle with the same name as the executable.
17

OPTIONS

19       --accelerator=<accelerator type>
20              Specify the desired type of accelerator table. Valid options are
21              'Apple', 'Dwarf', 'Default' and 'None'.
22
23       --arch <arch>
24              Link DWARF debug information only for specified CPU architecture
25              types.  Architectures may be specified by name. When using  this
26              option,  an  error will be returned if any architectures can not
27              be properly linked.   This  option  can  be  specified  multiple
28              times, once for each desired architecture. All CPU architectures
29              will be linked by default and any architectures  that  can't  be
30              properly linked will cause dsymutil to return an error.
31
32       --dump-debug-map
33              Dump  the  executable's  debug-map (the list of the object files
34              containing the debug information) in YAML format  and  exit.  No
35              DWARF link will take place.
36
37       --flat, -f
38              Produce a flat dSYM file. A .dwarf extension will be appended to
39              the executable name unless the output file  is  specified  using
40              the -o option.
41
42       --gen-reproducer
43              Generate  a  reproducer  consisting  of  the input object files.
44              Alias for --reproducer=GenerateOnExit.
45
46       --help, -h
47              Print this help output.
48
49       --keep-function-for-static
50              Make a static variable keep the enclosing function  even  if  it
51              would have been omitted otherwise.
52
53       --minimize, -z
54              When  used  when creating a dSYM file, this option will suppress
55              the emission of the .debug_inlines,  .debug_pubnames,  and  .de‐
56              bug_pubtypes sections since dsymutil currently has better equiv‐
57              alents: .apple_names and .apple_types. When used in  conjunction
58              with --update option, this option will cause redundant accelera‐
59              tor tables to be removed.
60
61       --no-odr
62              Do not use ODR (One Definition Rule) for uniquing C++ types.
63
64       --no-output
65              Do the link in memory, but do not emit the result file.
66
67       --no-swiftmodule-timestamp
68              Don't check the timestamp for swiftmodule files.
69
70       --num-threads <threads>, -j <threads>
71              Specifies the maximum number (n) of simultaneous threads to  use
72              when linking multiple architectures.
73
74       --object-prefix-map <prefix=remapped>
75              Remap object file paths (but no source paths) before processing.
76              Use this for Clang objects where the module cache  location  was
77              remapped  using  -fdebug-prefix-map;  to  help dsymutil find the
78              Clang module cache.
79
80       --oso-prepend-path <path>
81              Specifies a path to prepend to  all  debug  symbol  object  file
82              paths.
83
84       --out <filename>, -o <filename>
85              Specifies  an  alternate  path to place the dSYM bundle. The de‐
86              fault dSYM bundle path is created by appending .dSYM to the exe‐
87              cutable name.
88
89       --papertrail
90              When  running  dsymutil  as part of your build system, it can be
91              desirable for warnings to be part of  the  end  product,  rather
92              than just being emitted to the output stream. When enabled warn‐
93              ings are embedded in the linked DWARF debug information.
94
95       --remarks-output-format <format>
96              Specify the format to be used when serializing  the  linked  re‐
97              marks.
98
99       --remarks-prepend-path <path>
100              Specify  a directory to prepend the paths of the external remark
101              files.
102
103       --reproducer <mode>
104              Specify the reproducer generation mode. Valid options are  'Gen‐
105              erateOnExit', 'GenerateOnCrash', 'Use', 'Off'.
106
107       --statistics
108              Print  statistics  about the contribution of each object file to
109              the linked debug info. This prints a table  after  linking  with
110              the  object  file name, the size of the debug info in the object
111              file (in bytes) and the  size  contributed  (in  bytes)  to  the
112              linked  dSYM. The table is sorted by the output size listing the
113              object files with the largest contribution first.
114
115       --symbol-map <bcsymbolmap>
116              Update the existing dSYMs inplace using symbol map specified.
117
118       -s, --symtab
119              Dumps the symbol table found in executable or object file(s) and
120              exits.
121
122       -S     Output textual assembly instead of a binary dSYM companion file.
123
124       --toolchain <toolchain>
125              Embed the toolchain in the dSYM bundle's property list.
126
127       -u, --update
128              Update  an  existing dSYM file to contain the latest accelerator
129              tables and other DWARF optimizations. This option  will  rebuild
130              the '.apple_names' and '.apple_types' hashed accelerator tables.
131
132       --use-reproducer <path>
133              Use  the  object files from the given reproducer path. Alias for
134              --reproducer=Use.
135
136       --verbose
137              Display verbose information when linking.
138
139       --verify
140              Run the DWARF verifier on the linked DWARF debug info.
141
142       -v, --version
143              Display the version of the tool.
144
145       -y     Treat executable as a YAML debug-map rather than an executable.
146

EXIT STATUS

148       dsymutil returns 0 if the DWARF debug information was  linked  success‐
149       fully. Otherwise, it returns 1.
150

SEE ALSO

152       llvm-dwarfdump(1)
153

AUTHOR

155       Maintained by the LLVM Team (https://llvm.org/).
156
158       2003-2023, LLVM Project
159
160
161
162
16315                                2023-07-20                       DSYMUTIL(1)
Impressum