#crash-reporting #crash-reports #minidump #linux #processor #thread


A library for producing stack traces and other useful information from minidump files

26 releases (12 breaking)

0.19.1 Nov 2, 2023
0.18.0 Sep 18, 2023
0.17.0 May 17, 2023
0.15.2 Dec 7, 2022
0.1.0 Dec 21, 2017

#53 in Debugging

Download history 294/week @ 2023-08-13 153/week @ 2023-08-20 269/week @ 2023-08-27 318/week @ 2023-09-03 272/week @ 2023-09-10 329/week @ 2023-09-17 230/week @ 2023-09-24 744/week @ 2023-10-01 1346/week @ 2023-10-08 667/week @ 2023-10-15 814/week @ 2023-10-22 507/week @ 2023-10-29 426/week @ 2023-11-05 2079/week @ 2023-11-12 487/week @ 2023-11-19 1800/week @ 2023-11-26

4,820 downloads per month
Used in 5 crates (4 directly)

MIT license

27K SLoC



A library for producing stack traces and other useful information from minidump files. This crate provides APIs for producing symbolicated stack traces for the threads in a minidump, as well as a minidump_stackwalk tool that is intended to function very similarly to the one in the Google Breakpad project.

The JSON Schema is stable and documented here.

If you want lower-level access to the minidump's contents, use the minidump crate.

For a CLI application that wraps this library, see minidump-stackwalk. This is the primary and stable interface for minidump-processor, which we recommend for most production users.

For a GUI application that wraps this library, see minidump-debugger. This is an experimental external project.

If you do need to use minidump-processor as a library, we still recommend using the stabilized JSON output. The native APIs work fine and contain all the same information, we just haven't stabilized them yet, so updates are more likely to result in breakage. Here is a minimal example which gets the JSON output (and parses it with serde_json):

use minidump::Minidump;
use minidump_processor::ProcessorOptions;
use minidump_unwind::{http_symbol_supplier, Symbolizer};
use serde_json::Value;

async fn main() -> Result<(), ()> {
    // Read the minidump
    let dump = Minidump::read_path("../testdata/test.dmp").map_err(|_| ())?;
    // Configure the symbolizer and processor
    let symbols_urls = vec![String::from("https://symbols.totallyrealwebsite.org")];
    let symbols_paths = vec![];
    let mut symbols_cache = std::env::temp_dir();
    let symbols_tmp = std::env::temp_dir();
    let timeout = std::time::Duration::from_secs(1000);
    // Use ProcessorOptions for detailed configuration
    let options = ProcessorOptions::default();

    // Specify a symbol supplier (here we're using the most powerful one, the http supplier)
    let provider = Symbolizer::new(http_symbol_supplier(
    let state = minidump_processor::process_minidump_with_options(&dump, &provider, options)
        .map_err(|_| ())?;

    // Write the JSON output to an arbitrary writer (here, a Vec).
    let mut json_output = Vec::new();
    state.print_json(&mut json_output, false).map_err(|_| ())?;

    // Now parse it (here parsed into an arbitrary JSON Object for max flexibility).
    let json: Value = serde_json::from_slice(&json_output).map_err(|_| ())?;

    // Now read whatever values you want out of it
    if let Some(Value::Number(pid)) = json.get("pid") {
        println!("pid: {}", pid);



~403K SLoC