8 unstable releases (3 breaking)

0.4.0 Jul 20, 2021
0.3.3 May 14, 2021
0.3.0 Apr 23, 2021
0.2.0 Mar 23, 2021
0.1.2 Mar 13, 2021
Download history 6/week @ 2022-06-09 5/week @ 2022-06-16 4/week @ 2022-06-23 5/week @ 2022-06-30 18/week @ 2022-07-07 10/week @ 2022-07-14 29/week @ 2022-07-21 30/week @ 2022-07-28 123/week @ 2022-08-04 102/week @ 2022-08-11 115/week @ 2022-08-18 69/week @ 2022-08-25 126/week @ 2022-09-01 109/week @ 2022-09-08 62/week @ 2022-09-15 179/week @ 2022-09-22

489 downloads per month
Used in pdbview

MIT license


API Documentation] crates.io


A high-level library for the fantastic pdb crate


The pdb crate provides a low-level interface for interacting with PDB files. While the crate provides very good and useful information, it may not be the easiest solution for looking at the whole slice of a PDB. From the pdb crate's README:

pdb's design objectives are similar to gimli:

  • pdb works with the original data as it's formatted on-disk as long as possible.

  • pdb parses only what you ask.

  • pdb can read PDBs anywhere. There's no dependency on Windows, on the DIA SDK, or on the target's native byte ordering.

The first two bullet points in particular can be particularly cumbersome if your application needs to iterate over every type, find one of a particular size or containing a particular field, and perform some operations on it. While you absolutely should care about speed and not performing unnecessary work, sometimes the reality is that you simply don't. This crate is for those scenarios where you just want to hack on some data and speed is not a concern.

The biggest differences are that ezpdb takes care of building the type heirarchy and copies all necessary information for ease of use.


let parsed_pdb = ezpdb::parse_pdb(&opt.file, opt.base_address)?;
println!("{:?}", parsed_pdb.assembly_info);


~34K SLoC