You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking to fuzz the library more and use the fuzzer to compare the output to the reference C implementation. I've been wondering, what's the difference between the two directories with inputs - decodecorpus_files and fuzz_decodecorpus?
Also, you can make cargo-fuzz automatically pick up the fuzzing corpus without requiring to explicitly specify a path if you move it to fuzz/corpus/fuzz_target_1, similar to artifacts folder.
The text was updated successfully, but these errors were encountered:
The two different dirs are more or less out of lazyness. One is used for testing (so I have a few files and the originals together in one dir) and one is input for fuzzing, and only contains .zst files.
Cool, I did not know I could setup the corpus like that!
If you find any crashes / timeouts please let me know, I do care about this crates correctness. Always glad to have a second pair of eyes look at my stuff :)
I'm looking to fuzz the library more and use the fuzzer to compare the output to the reference C implementation. I've been wondering, what's the difference between the two directories with inputs - decodecorpus_files and fuzz_decodecorpus?
Also, you can make cargo-fuzz automatically pick up the fuzzing corpus without requiring to explicitly specify a path if you move it to
fuzz/corpus/fuzz_target_1
, similar toartifacts
folder.The text was updated successfully, but these errors were encountered: