fix: weight corpus by timestamp to favor 'hardest-to-discover' inputs#383
Merged
fix: weight corpus by timestamp to favor 'hardest-to-discover' inputs#383
Conversation
anishnaik
approved these changes
Jan 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When the fuzzer is restarted, it currently weights all seeds equally despite use the aggregate call count as it does at runtime. The thinking is that an input that took the longest to discover. Using the timestamp of the corpus sort of approximates using the call count at runtime (time and call count both increase as the fuzzer runs). This is how Echidna does it fwiw