Skip to content

Support advanced libFuzzer arguments with @FuzzTest #478

@fmeum

Description

@fmeum

Makes sense. I've been using -merge to save off different corpus directories at different stages and then merge them back into one corpus later on. I guess I was wondering more generally about all the LibFuzzer single-dash options, which the CLI docs seem to punt as "just go read the LibFuzzer docs and do whatever you want", so I was wondering if the same approach was planned here... -merge being the main place where I've taken advantage of this flexibility (so far).

Originally posted by @gredler in #475 (comment)

I don't have a fully fleshed out plan yet for how to deal with these "advanced" libFuzzer flags. I would like to keep them out of the @fuzztest annotation, which should offer a friendly UX to users new to fuzzing. Instead, I'm thinking of making Jazzer available as a standalone JAR used from the CLI and/or making it possible to tune libFuzzer arguments via system properties.

_Originally posted by @fmeum

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions