Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Draft
wants to merge 2 commits into
base: dev
Choose a base branch
from

Commits on Jan 4, 2024

  1. More flexibility when creating fuzzers at the cost of Fuzzers requiri…

    …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).
    Michael Rodler committed Jan 4, 2024
    Configuration menu
    Copy the full SHA
    17744f5 View commit details
    Browse the repository at this point in the history

Commits on Jan 9, 2024

  1. Fuzzer is now initialized with new(project_state) and cloned across…

    … all commands.
    Michael Rodler committed Jan 9, 2024
    Configuration menu
    Copy the full SHA
    0b0f09d View commit details
    Browse the repository at this point in the history