Oopsie woopsie!

A crate to make debugging unexpected panics easier both on developer and consumer machines. Gives you a panic handler which generates a backtrace, backtrace frames (with symbols) and a minidump.

Reminder: You should always have an out-of-process crash handler incase of a crash. This crate only handles panics. It is recommended to use Breakpad or Crashpad.

Features

• Creates a backtrace and a list of backtrace frames with symbols.
• Creates a minidump.
• Prints the panic information to stderr.
• Writes the backtraces and minidump to a specified location (Backtrace file location and minidump file location separately configured).

Usage example

``` panic::sethook(Box::new(|panicinfo: &panic::PanicInfo| { // The paths to where the log files will be written to (Must also have a filename, such as "C:\Example\paniclog.txt"). // Existing files with the same filename will get overwritten. let paniclogfiledestination: String = r"C:\exampledir\paniclog.txt".tostring(); // The path where the panic log will be written to (Stderr output but also with backtrace frames). let minidumpfiledestionation: String = r"C:\exampledir\minidump.mdmp".tostring(); // The path where the minidump will be written to. Preferrably with a .mdmp extension.

    // Replaces the default panic handler with the custom made one.
    error_handler::handle_error(panicinfo, panic_log_file_destination, minidump_file_destionation);

})); ```