More flexibility when creating fuzzers at the cost of Fuzzers requiring Clone + Send.
#36
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
added 2 commits
January 4, 2024 11:51
…ng `Clone + Send`.
* Added `Fuzzer::load_seed_input` to allow additional or different handling
of seed inputs, e.g., parsing seed files that are then stored in a
different format internally and in the corpus (e.g., parsing source
code into an AST and then doing AST mutations).
* A fuzzer is now constructed with `FUZZER::new` once and then cloned
for every core. As a consequence fuzzers are now `Clone + Send`. This
allows for several patterns:
* Custom shared state across all cores, e.g., for custom metadata.
* Performing costly initialization only once (e.g., parsing a system call
definition file).
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.
Fuzzer::load_seed_inputto allow additional or different handling of seed inputs, e.g., parsing seed files that are then stored in a different format internally and in the corpus (e.g., parsing source code into an AST and then doing AST mutations).FUZZER::newonce and then cloned for every core. As a consequence fuzzers are nowClone + Send. This allows for several patterns: