Trigger feedback side effects during force-loading #1317
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During some experimentation, I noticed that calling
load_initial_inputs_forced
rather thanload_initial_inputs
made a significant impact on the code coverage of my fuzzer.This was because
load_initial_inputs_forced
does not evaluate feedbacks (or objectives), so the code coverage of the initial corpus elements wasn't recorded.While this might be seem significant for very long running fuzzing sessions, it means that other inputs will be added to the corpus that wouldn't otherwise be interesting (because their code coverage is included in the initial corpus elements).
Therefore, I believe that the correct behaviour of
load_initial_inputs_forced
is to trigger the side-effects of feedbacks and objectives, but then consider the inputs interesting (and not solutions). Alternatively, we could change how feedbacks are implemented not to use side-effects this way.Please let me know if I'm missing something here!