[WIP] adding more fuzzing targets #55
Closed
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
|
Awesome, thanks! Do you have any feelings on libfuzzer vs. honggfuzz? You might have noticed there's also an I feel like unless there's a good reason otherwise, it'll be easiest to stick to one fuzzing library. (by that I mean I'd be happy to switch to cargo-fuzz/libfuzzer if it makes sense to). |
|
Ah! #28 was about more cases not different fuzzing tools? I have no strong opinions. I'll set them up with hfuzz instead. |
|
sounds good! |
|
wow, didn't realize you force-pushed the changes a while back! rebased your commit and merged it - thanks so much again and nice find! |
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.
First pass at #28 with a test case for the first finding. I'll add more fuzz targets