Repository navigation
Isolated Processes 11: Use a user-chosen handler for drop failures #199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| //! 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) | ||
|
|
||
| use core::sync::atomic::{AtomicPtr, Ordering}; | ||
|
|
||
| static HANDLER: AtomicPtr<Handler> = AtomicPtr::new(core::ptr::null_mut()); | ||
|
|
||
| pub struct Handler { | ||
| pub(crate) f: for<'a> fn(core::fmt::Arguments<'a>), | ||
| } | ||
|
|
||
| impl Handler { | ||
| /// Decorate the given function as a potential global Drop handler | ||
| pub const fn new(f: for<'a> fn(core::fmt::Arguments<'a>)) -> Self { | ||
| Self { f } | ||
| } | ||
| /// Install this handler as the new global Drop handler | ||
| /// | ||
| /// Will overwrite any previously installed handler | ||
| pub fn install_global(&'static self) { | ||
| HANDLER.store((self as *const Handler).cast_mut(), Ordering::Release); | ||
| } | ||
| } | ||
|
|
||
| pub(crate) fn get() -> Option<&'static Handler> { | ||
| let ptr: *const Handler = HANDLER.load(Ordering::Acquire).cast_const(); | ||
| if ptr.is_null() { | ||
| None | ||
| } else { | ||
| Some(unsafe { &*ptr }) | ||
| } | ||
| } | ||
|
|
||
| macro_rules! report_drop_failed(($($arg: tt)*) => {{ | ||
| if let Some(handler) = $crate::drop_fail_handler::get() { | ||
| (handler.f)(::core::format_args!($($arg)*)); | ||
| } | ||
| }}); | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.