DevComp/zip-rs-wasm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

chore: Use panic! rather than abort to ensure the fuzz harness can process the failure

Browse source
This commit is contained in:
Chris Hennick 2024-05-05 20:17:12 -07:00
parent f2b55a1f59
commit 0011370fdc
No known key found for this signature in database
GPG key ID: DA47AABA4961C509
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
fuzz/fuzz_targets/fuzz_write.rs
View file

@ -2,7 +2,7 @@
use arbitrary::Arbitrary;
use libfuzzer_sys::fuzz_target;
use replace_with::replace_with_or_abort;
use replace_with::replace_with;
use std::io::{Cursor, Read, Seek, Write};
use std::path::PathBuf;
@ -83,7 +83,9 @@ where
}
if operation.reopen {
let old_comment = writer.get_raw_comment().to_owned();
replace_with_or_abort(writer, |old_writer: zip::ZipWriter<T>| {
replace_with(writer, || {
panic!("Failed to reopen writer");
}, |old_writer: zip::ZipWriter<T>| {
let new_writer =
zip::ZipWriter::new_append(old_writer.finish().unwrap()).unwrap();
assert_eq!(&old_comment, new_writer.get_raw_comment());