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.

Sign up for GitHub

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

Jump to bottom

detect bad fuzzing #31

Open

fuzzah opened this issue Oct 9, 2023 · 1 comment

Labels

enhancement good first issue

Member

fuzzah commented Oct 9, 2023

It would be good to detect the following situations and bail with bad exit code:

No fuzz stats for some time after beginning to fuzz. Note: for AFL++ there are no stats until the initial corpus was loaded, which on some binaries can take more than 30 minutes.
Bad coverage generated, e.g. 0% coverage.
Bad report generated, e.g. 0 fuzz instances, blank screenshots, 0% coverage, ...
Something else?

fuzzah added enhancement good first issue labels

Member Author

fuzzah commented Oct 27, 2023

Something else:
4. Detect fuzzers being stopped by OOM-killer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment