| drop_fail_handler.rs |
Set a custom handler for when a Drop failure occurs
Normally, there is not much that can be done when an error occurs during execution of `drop()`
-- Common strategies are to just ignore it, or to just log it and ignore it.
We prefer the latter approach, but the issue is that if a Rust global logger has been set up
in the crashed process that will run the Executor, that could result in `log` being used in
a signal handler context. And since common logging behavior is to print to stderr, that will
almost-certainly cause a deadlock or some kind of other re-entrancy issue.
Instead, we don't prescribe a behavior - We allow the user of minidump-writer to set their
own handler for failed `drop()` calls. If the user knows it's safe to log or print or
whatever, they can do that.
Note that using [`install_global()`] to install a new handler will always overwrite any
previously-installed handler. This is intentional, as the user of this crate may want to
disable a previously-installed handler after a crash occurs (if that handler would cause
re-entrancy issues) |
2178 |
- |
| lib.rs |
|
3009 |
- |
| local |
|
|
- |
| regs.rs |
|
16590 |
- |
| wrapper.rs |
|
989 |
- |