Skip to content

Bug when starting from a large corpus #137

@louismerlin

Description

@louismerlin

When starting a fuzzer from a large corpus with many cores, and the input corpus is in the default corpus directory, the fuzzers have a great chance of stopping with the "short read" error message.

This does not happen anymore when I use the -i parameter to select another initial corpus directory.

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