#crash #minidump #ipc #out-of-process


IPC impl for creating a minidump for a crashed process

8 releases (5 breaking)

0.8.0 Apr 3, 2023
0.7.0 Nov 17, 2022
0.6.0 Oct 21, 2022
0.5.1 Sep 2, 2022
0.3.1 May 25, 2022

#421 in Debugging

Download history 2957/week @ 2023-07-30 2615/week @ 2023-08-06 598/week @ 2023-08-13 579/week @ 2023-08-20 573/week @ 2023-08-27 747/week @ 2023-09-03 534/week @ 2023-09-10 595/week @ 2023-09-17 552/week @ 2023-09-24 1121/week @ 2023-10-01 1894/week @ 2023-10-08 822/week @ 2023-10-15 1116/week @ 2023-10-22 583/week @ 2023-10-29 574/week @ 2023-11-05 2340/week @ 2023-11-12

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


2.5K SLoC

🔥 minidumper

IPC implementation for creating a minidump for a crashed process

Embark Embark Crates.io Docs dependency status Build status

This crate supplies a client and server IPC implementation for communicating between a process that may crash (client) and a monitor (server) process.

The client can communicate application-specific state via Client::send_message, and, if a crash occurs, can use Client::request_dump to request a minidump be created. The Server uses a user implemented ServerHandler to handle the messages sent by the client, and provides a way to create the minidump file where a requested crash can be written to, as well as a callback when a minidump is finished writing (both on failure and success) to perform whatever additional steps make sense for the application, such as transmission of the minidump to an external HTTP service for processing or the like.


Contributor Covenant

We welcome community contributions to this project.

Please read our Contributor Guide for more information on how to get started. Please also read our Contributor Terms before you make any contributions.

Any contribution intentionally submitted for inclusion in an Embark Studios project, shall comply with the Rust standard licensing model (MIT OR Apache 2.0) and therefore be dual licensed as described below, without any additional terms or conditions:


This contribution is dual licensed under EITHER OF

at your option.

For clarity, "your" refers to Embark or any other licensee/user of the contribution.


~145K SLoC