cargo fuzz harness and fixes for bugs found #51
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Twinklebear
approved these changes
Jul 9, 2022
|
Thanks for these fixes and the fuzzer @evanrichter ! Everything looks good to me, I'll push out a release with these fixes now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! I wrote a couple fuzzers targeting file loading (mtl and obj). The mtl fuzzer did not find any issues (running for a couple hours). The obj loader, which is more complex of course, did find several panics when reading corrupting files.
The fuzzers are in the fuzz directory, as is common for cargo-fuzz.