-
Notifications
You must be signed in to change notification settings - Fork 269
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
Fix duplicate hash logic #868
Merged
Merged
Conversation
This file contains 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
1 task
This was referenced Jul 17, 2024
This was referenced Aug 2, 2024
This was referenced Aug 6, 2024
This was referenced Aug 16, 2024
This was referenced Sep 19, 2024
This was referenced Sep 24, 2024
This was referenced Oct 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In #854 (v0.8.7) logic was added to the collector that filters duplicate consecutive hashes because viaIR was doing that and messing up the hit counts.
However #863 reports a case where these duplicates are expected - they're inheriting onlyOwner and testing the implementation by switching the EOA e.g
The instrumentation looks like:
function a() preCondition onlyOwner postCondition {}
...so running the failure and success case one after another gives
PR adds logic to make sure this filtering only happens within a single transaction (frame?) using program counter tracking.