introduce fuzz testing of the library using llvm libfuzzer#150
Draft
introduce fuzz testing of the library using llvm libfuzzer#150
Conversation
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against 045c13f |
rdmark
force-pushed
the
fuzz-testing
branch
7 times, most recently
from
bb94728 to
1d1bfd1
Compare
with clang and llvm's libfuzzer, fuzzed data can be fed into the functions under test to stress test them with random input values
|
Collaborator
Author
|
running the fuzzing locally on my Debian Trixie machine led to two bugs being found
will keep this PR as draft until these have been merged |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
with clang and llvm's libfuzzer, fuzzed data can be fed into the functions under test to stress test them with random input values