Skip to content
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

Any difference between decodecorpus_files and fuzz_decodecorpus? #5

Open
Shnatsel opened this issue Apr 17, 2020 · 1 comment
Open

Comments

@Shnatsel
Copy link
Contributor

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.

@KillingSpark
Copy link
Owner

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants