shaba/ostree
1
0
Fork 0
mirror of https://github.com/ostreedev/ostree.git synced 2024-12-22 17:35:55 +03:00
Code Issues Projects Releases Wiki Activity

repo: Avoid potential double unwind when writing panic value

Browse Source 
Thanks to @shinmao for the report!

Closes: https://github.com/ostreedev/ostree/issues/2775
This commit is contained in:
Colin Walters 2022-11-18 11:26:46 -05:00
parent 9d652be3b1
commit a4f5645926
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
rust-bindings/src/repo_checkout_at_options/repo_checkout_filter.rs
View File

@ -107,18 +107,26 @@ pub(super) unsafe extern "C" fn filter_trampoline_unwindsafe(
///
/// If the panic value is either `&str` or `String`, we print it. Otherwise, we don't.
fn print_panic(panic: Box<dyn Any>) {
eprintln!("A Rust callback invoked by C code panicked.");
eprintln!("Unwinding across FFI boundaries is Undefined Behavior so abort() will be called.");
use std::io::Write;
let stderr = std::io::stderr();
let mut stderr = stderr.lock();
// Directly write to stderr instead of eprintln!() as that function panics
// if writing fails, which would involve a double panic which we don't want.
let _ = stderr.write_all(
r#"A Rust callback invoked by C code panicked.
Unwinding across FFI boundaries is Undefined Behavior so abort() will be called."#
.as_bytes(),
);
let msg = {
if let Some(s) = panic.as_ref().downcast_ref::<&str>() {
s
} else if let Some(s) = panic.as_ref().downcast_ref::<String>() {
s
} else {
"UNABLE TO SHOW VALUE OF PANIC"
"(non-string panic value)"
}
};
eprintln!("Panic value: {}", msg);
let _ = stderr.write_all(msg.as_bytes());
}
#[cfg(test)]