Open LegionMammal978 opened 1 year ago
Ah, should look at finding some other way to handle that then
And yeah miniz isn't designed to explicitly panic anywhere (though it's plausible that improper use of the unsafe c api bits could cause out of bounds panics or similar.)
The
miniz_oxide_c_api
wrappers insrc/lib.rs
callprintln!("FATAL ERROR: Caught panic!");
when a panic is caught.println!()
can panic if it fails to write, causing UB ifpanic = "abort"
is not set. Replacing it withlet _ = write!(io::stdout(), "FATAL ERROR: Caught panic!");
would make it ignore any write errors.(As a side note, I tried to find any code paths that actually cause a panic, but could not find any. Is
miniz_oxide
designed to never panic in the absence of bugs?)