Add PCRE2 as a fuzzing benchmark #2034
Draft
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
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.
PCRE2 is a complicated target which is prone to timeouts. This timeout-proneness is caused, in part, by the input representing instructions rather than flat data. Additionally, the state space of the program is significantly larger than the code coverage suggests. These two issues together make this a very hard target to fuzz, which has led to interesting problems in OSS-Fuzz and in local testing.
I think this target is interesting from a benchmarking perspective as it introduces complications which are not present in other targets in Fuzzbench and would like to add it to the standard benchmark suite. I have used the standard OSS-Fuzz integration script.
CC @PhilipHazel @alexdowad for input.