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       --arch=<arch>
20              Link DWARF debug information only for specified CPU architecture
21              types.   Architectures may be specified by name. When using this
22              option, an error will be returned if any architectures  can  not
23              be  properly  linked.   This  option  can  be specified multiple
24              times, once for each desired architecture. All CPU architectures
25              will  be  linked  by default and any architectures that can't be
26              properly linked will cause dsymutil to return an error.
27
28       --dump-debug-map
29              Dump the executable's debug-map (the list of  the  object  files
30              containing  the  debug information) in YAML format and exit. Not
31              DWARF link will take place.
32
33       -f, --flat
34              Produce a flat dSYM file. A .dwarf extension will be appended to
35              the  executable  name  unless the output file is specified using
36              the -o option.
37
38       -z, --minimize
39              When used when creating a dSYM file, this option  will  suppress
40              the  emission  of  the .debug_inlines, .debug_pubnames, and .de‐
41              bug_pubtypes sections since dsymutil currently has better equiv‐
42              alents:  .apple_names and .apple_types. When used in conjunction
43              with --update option, this option will cause redundant accelera‐
44              tor tables to be removed.
45
46       --no-odr
47              Do not use ODR (One Definition Rule) for uniquing C++ types.
48
49       --no-output
50              Do the link in memory, but do not emit the result file.
51
52       --no-swiftmodule-timestamp
53              Don't check the timestamp for swiftmodule files.
54
55       -j <n>, --num-threads=<n>
56              Specifies  the maximum number (n) of simultaneous threads to use
57              when linking multiple architectures.
58
59       -o <filename>
60              Specifies an alternate path to place the dSYM  bundle.  The  de‐
61              fault dSYM bundle path is created by appending .dSYM to the exe‐
62              cutable name.
63
64       --oso-prepend-path=<path>
65              Specifies a path to prepend to  all  debug  symbol  object  file
66              paths.
67
68       --papertrail
69              When  running  dsymutil  as part of your build system, it can be
70              desirable for warnings to be part of  the  end  product,  rather
71              than just being emitted to the output stream. When enabled warn‐
72              ings are embedded in the linked DWARF debug information.
73
74       -s, --symtab
75              Dumps the symbol table found in executable or object file(s) and
76              exits.
77
78       --toolchain
79              Embed the toolchain in the dSYM bundle's property list.
80
81       -u, --update
82              Update  an  existing dSYM file to contain the latest accelerator
83              tables and other DWARF optimizations. This option  will  rebuild
84              the '.apple_names' and '.apple_types' hashed accelerator tables.
85
86       -v, --verbose
87              Display verbose information when linking.
88
89       --version
90              Display the version of the tool.
91
92       -y     Treat executable as a YAML debug-map rather than an executable.
93

EXIT STATUS

95       dsymutil  returns  0 if the DWARF debug information was linked success‐
96       fully. Otherwise, it returns 1.
97

SEE ALSO

99       llvm-dwarfdump(1)
100

AUTHOR

102       Maintained by The LLVM Team (http://llvm.org/).
103

105       2003-2023, LLVM Project
106
107
108
109
1107                                 2023-07-20                       DSYMUTIL(1)
Impressum