Crate human_panic 

Panic messages for humans

Reduce the effort for users to report panics back to you

You can still get the raw output by either:

• Running a debug build
• Setting RUST_BACKTRACE=1

Example

Add to your fn main():

human_panic::setup_panic!();

When run locally in a release build:

my-program had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "/var/folders/zw/bpfvmq390lv2c6gn_6byyv0w0000gn/T/report-8351cad6-d2b5-4fe8-accd-1fcbf4538792.toml". Submit an issue or email with the subject of "human-panic Crash Report" and include the report as an attachment.

- Homepage: https://github.com/rust-ci/human-panic
- Authors: Yoshua Wuyts <yoshuawuyts@gmail.com>

We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!

Traditional output:

thread 'main' panicked at 'oops', examples/main.rs:2:3
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Modules

report

This module encapsulates the report of a failure event.

Macros

metadata

Collect Cargo Metadata

setup_panic

Register human-panic

Structs

Metadata

A convenient metadata struct that describes a crate

Enums

PanicStyle

Style of panic to be used

Functions

handle_dump

Utility function which will handle dumping information to disk

print_msg

Utility function that prints a message to our human users