Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
DSYMUTIL(1)			     LLVM			   DSYMUTIL(1)

       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  con-
       tained in its symbol table. By default, the linked debug	information is
       placed in a .dSYM bundle	with the same name as the executable.

	      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 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.

       -z, --minimize
	      When used	when creating a	dSYM file, this	option	will  suppress
	      the  emission  of	 the .debug_inlines, .debug_pubnames, and .de-
	      bug_pubtypes sections since dsymutil currently has better	equiv-
	      alents:  .apple_names and	.apple_types. When used	in conjunction
	      with --update option, this option	will cause redundant accelera-
	      tor tables to be removed.

	      Do not use ODR (One Definition Rule) for uniquing	C++ types.

	      Do the link in memory, but do not	emit the result	file.

	      Don't check the timestamp	for swiftmodule	files.

       -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  de-
	      fault dSYM bundle	path is	created	by appending .dSYM to the exe-
	      cutable name.

	      Specifies	a path to prepend to  all  debug  symbol  object  file

	      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 warn-
	      ings are embedded	in the linked DWARF debug information.

       -s, --symtab
	      Dumps the	symbol table found in executable or object file(s) and

	      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.

       -v, --verbose
	      Display verbose information when linking.

	      Display the version of the tool.

       -y     Treat executable as a YAML debug-map rather than an executable.

       dsymutil	 returns  0 if the DWARF debug information was linked success-
       fully. Otherwise, it returns 1.


       Maintained by the LLVM Team (

       2003-2022, LLVM Project

9				  2022-11-17			   DSYMUTIL(1)


Want to link to this manual page? Use this URL:

home | help