benchmark mode: until first bug or until timeout #6
Conversation
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
Collaborator
|
Thank you for the suggestion. However, it seems challenging to decide whether the fuzzer had really found the bug that we originally targeted. Since there may exist multiple bugs (and different kind of bugs) in one contract, I'm concerned that it can be incorrect to use this mode to estimate the time-to-exposure of a specific bug. |
Author
|
@jchoi2022 I agree. However, I used this primarily to test on smart contracts that only contain a single bug. Then you don't have this problem at all. |
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.
useful for benchmarking smartian and comparing to other tools according to "time-to-bug".