This manual page is part of Xcode Tools version 3.2.2

To obtain these tools:

If you are running a version of Xcode Tools other than 3.2.2, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.



dwarfdump(1)                             BSD General Commands Manual                            dwarfdump(1)

NAME
     dwarfdump -- dump DWARF debug information.

SYNOPSIS
     dwarfdump [options] file1 file2 ...

DESCRIPTION
     For each operand that names a mach-o or 32 bit ELF file, dwarfdump disassembles the DWARF data found
     within the file. Only the .debug_info section is disassembled unless one of the --debug-XXXX or --all
     options are specified.

     The following options are available:

     -a, --all
              Disassemble all supported DWARF sections.

     --arch=ARCH
              Dump DWARF debug information for the specified CPU architecture.  Architectures may be speci-fied specified
              fied by name or by number.  This option can be specified multiple times, once for each desired
              architecture.  All cpu architectures will be disassembled by default.

     -c, --show-children
              Show a DIE's children when using the --debug-info=OFFSET, --find, and --name options.

     -e, --english
              Print dwarf tags and attributes in a more readable format instead of using the DWARF TAG_ and
              AT_ definitions.

     --eh-frame[=SECTION]
              Dump exception handling frame information from the optional SECTION parameter.  The __eh_frame
              section will be dumped by default.

     --file-stats[=size]
              Show file composition statistics for any input files. Each file's contents are analyzed and
              broken down into byte counts for the following categories: symbol table, string table, text
              and code, DWARF debug information, STABS debug information, and other. When multiple files are
              specified, byte count totals for each category will be displayed at the end of the table.
              Specify the optional 'size' argument to show all byte count results using unit suffixes: Byte,
              Kilobyte, Megabyte, Gigabyte, Terabyte and Petabyte. This option can be useful in tracking the
              size and makeup of mach-o binary files, and also allows easy comparison between DWARF and
              STABS built binaries and related object files.

     -f PATTERN, --find=PATTERN
              Search for the exact text PATTERN in the .debug_pubnames section and print the matching debug
              information entries. Use the --regex option to have PATTERN become a regular expression for
              more flexible pattern matching.

              When there is no .debug_pubnames section or the name of the DIE you are looking for is not
              found in the .debug_pubnames section, try using the slower but more complete --name option.

     -F, --show-form
              Show DWARF form types after the DWARF attribute types.

     -h, -?, --help
              Show help and usage for this command.

     -i, --ignore-case
              Ignore case distinctions in when finding by name using strings or regular expressions.

     -n -PATTERN, --name=PATTERN
              Find and print all DIE entries whose name (DW_AT_name attribute) matches the exact text in
              PATTERN. Use the --regex option to have PATTERN become a regular expression for more flexible
              pattern matching.

     --lookup=ADDRESS
              Lookup ADDRESS in the debug information and print out the file, function, block and line table
              details.

     -o PATH, --out-file=PATH
              Redirect output to a file specified by PATH.

     -p, --show-parents
              Show a DIE's parent DIE objects when using the --debug-info=OFFSET, --find, and --name
              options.

     -r N, --recurse-depth=N
              Only recurse to a child depth of N when displaying the DWARF information.

     -x, --regex
              Treat any PATTERN strings as regular expressions when searching instead of just as an exact
              string match.

     -u, --uuid
              Show the UUID for each architecture.

     -v, --verbose
              Display verbose information when dumping. This can help to debug DWARF issues.

     --verify
              Verify the structure of the DWARF information by verifying the compile unit chains, die rela-tionships relationships
              tionships graph, and address ranges.

     --version
              Display the current version and build date of the dwarfdump binary.

     --debug-abbrev, --debug-aranges, --debug-frame[=OFFSET], --debug-info[=OFFSET], --debug-inlined,
              --debug-line[=OFFSET], --debug-macinfo[=OFFSET], --debug-pubnames[=PATTERN],
              --debug-pubtypes[=PATTERN], --debug-str
              Dump the specified DWARF section by name. Only the .debug_info section is disassembled by
              default. Some entries support adding a '=OFFSET' as a way to provide an optional offset of the
              exact entry to dump within the respective section. When an OFFSET is provided, only the entry
              at that offset will be dumped, else the entire section will be dumped. Some options support an
              optional '=PATTERN' parameter that will search the section for an entry with a matching name.
              Children of items at OFFSETs can be dumped by also using the --show-children option where
              applicable.

SEE ALSO
     dsymutil(1)

Darwin                                          May 12, 2010                                          Darwin

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.

Did this document help you? Yes It's good, but... Not helpful...