pretty¶

IMPORTANT:

USAGE: llvm-pdbutil pretty [options] <input PDB file>

Summary¶

The pretty subcommand displays a very high level representation of your program’s debug info. Since it is built on the Windows DIA SDK which is the standard API that Windows tools and debuggers query debug information, it presents a more authoritative view of how a debugger is going to interpret your debug information than a mode which displays low-level CodeView records.

Options¶

Filtering and Sorting Options¶

NOTE:

Symbol Type Options¶

=all      - Display all class members including data, constants, typedefs, functions, etc (default)
=layout   - Only display members that contribute to class size.
=none     - Don't display class definitions (e.g. only display the name and base list)

=none            - Undefined / no particular sort order (default)
=name            - Sort classes by name
=size            - Sort classes by size
=padding         - Sort classes by amount of padding
=padding-pct     - Sort classes by percentage of space consumed by padding
=padding-imm     - Sort classes by amount of immediate padding
=padding-pct-imm - Sort classes by percentage of space consumed by immediate padding

=thunks - Display thunk symbols
=data   - Display data symbols
=funcs  - Display function symbols
=all    - Display all symbols (default)

=none - Undefined / no particular sort order
=name - Sort symbols by name
=size - Sort symbols by size

Other Options¶

dump¶

USAGE: llvm-pdbutil dump [options] <input PDB file>

Summary¶

The dump subcommand displays low level information about the structure of a PDB file. It is used heavily by LLVM’s testing infrastructure, but can also be used for PDB forensics. It serves a role similar to that of Microsoft’s cvdump tool.

NOTE:

Options¶

MSF Container Options¶

Module & File Options¶

Symbol Options¶

Type Record Options¶

Miscellaneous Options¶

bytes¶

USAGE: llvm-pdbutil bytes [options] <input PDB file>

Summary¶

Like the dump subcommand, the bytes subcommand displays low level information about the structure of a PDB file, but it is used for even deeper forensics. The bytes subcommand finds various structures in a PDB file based on the command line options specified, and dumps them in hex. Someone working on support for emitting PDBs would use this heavily, for example, to compare one PDB against another PDB to ensure byte-for-byte compatibility. It is not enough to simply compare the bytes of an entire file, or an entire stream because it’s perfectly fine for the same structure to exist at different locations in two different PDBs, and “finding” the structure is half the battle.

Options¶

MSF File Options¶

PDB Stream Options¶

DBI Stream Options¶

Module Options¶

Type Record Options¶

pdb2yaml¶

USAGE: llvm-pdbutil pdb2yaml [options] <input PDB file>

Summary¶

Options¶

yaml2pdb¶

USAGE: llvm-pdbutil yaml2pdb [options] <input YAML file>

Summary¶

Generate a PDB file from a YAML description. The YAML syntax is not described here. Instead, use llvm-pdbutil pdb2yaml and examine the output for an example starting point.

Options¶

Write the resulting PDB to the specified file.

merge¶

USAGE: llvm-pdbutil merge [options] <input PDB file 1> <input PDB file 2>

Summary¶

Merge two PDB files into a single file.

Options¶

Write the resulting PDB to the specified file.