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

Restart after n target executions, instead of n fuzz_loops #834

Open
domenukk opened this issue Oct 13, 2022 · 2 comments
Open

Restart after n target executions, instead of n fuzz_loops #834

domenukk opened this issue Oct 13, 2022 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@domenukk
Copy link
Member

So far, we have the option to restart an InProcess target after n rounds of fuzzing.

This means, however, that the number of target executions per round potentially grows after more testcases have been added to the corpus.
Instead, we should offer the option to restart after a fixed amount of iterations, to make sure targets leaking memory won't explode over time.
This could either be done by counting executions in the harness, and raising a signal accordingly (not taking it as objective), or by counting outside of the executor and retuning from the current stage.

@domenukk domenukk added the enhancement New feature or request label Oct 13, 2022
@andreafioraldi
Copy link
Member

A solution may be to generate an error in the run function of Fuzzer when execution() > limit

@andreafioraldi
Copy link
Member

We can add something like Error::RestartAsap

@domenukk domenukk added the help wanted Extra attention is needed label Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants