Skip to content

More flexibility when creating fuzzers at the cost of Fuzzers requiring Clone + Send.#36

Draft
f0rki wants to merge 2 commits intoawslabs:devfrom
f0rki:cloned-fuzzers
Draft

More flexibility when creating fuzzers at the cost of Fuzzers requiring Clone + Send.#36
f0rki wants to merge 2 commits intoawslabs:devfrom
f0rki:cloned-fuzzers

Conversation

@f0rki
Copy link
Copy Markdown

@f0rki f0rki commented Jan 4, 2024

  • 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).

Michael Rodler 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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant