fuzzing: add two new fuzzers to OSS-Fuzz setup #799
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
Signed-off-by: David Korczynski <david@adalogics.com>
DavidKorczynski
force-pushed
the
fuzzing-extension
branch
from
6709cea
to
e04a61f
Compare
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.
Adds two fuzzers to increase code coverage for OSS-Fuzz. From local runs, these fuzzers increase the coverage from ~44% to 73%+
The fuzzers rely on
FuzzedDataProviderto create data seeded with fuzz data, which means they are CPP files.For reference, I implemented these fuzzers as part of an instructional video on how to develop fuzzing harnesses link.