Add fuzzer#45
Merged
Merged
Conversation
seed corpus is generated from our unit tests
handle expected failures while generating the fuzzer seed corpus differently
MCLoebl
approved these changes
Oct 15, 2022
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
2 participants
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.
Add fuzzer for cgif which allows covering the complete API.
An initial seed corpus can be dynamically generated from our unit tests (
tests/).The seed corpus archive can be generated as follows:
meson setup build -Dfuzzer=truemeson test -C build> build/cgif_fuzzer_seed_corpus.zipNote: Generating a seed from a unit test is done by wrapping the cgif API (
fuzz/cgif_create_fuzz_seed.c). However, this wrapper does not emulate the cgif API entirely: Some unit tests are expected to fail when wrapped (e.g.tests/eindex.c).