bounty: fix slot overwrite bug on packed variables #117
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.
Bug description:
When variables are declared nearby (sometimes either in other abstract contract, but close on declaration order), using the
setVariable
method on one, can erase the information about the other variable.Given that
myAddress
(that occupies ~uint160
) andmyBool
are stored together, the secondsetVariable
method aims to the entire data slot and overwrites it with0x0000...1
(true
), and when themyAddress
slot is fetched, is filled with0
s.An example contract is added, and a test replicating the descripted bug.