-
Notifications
You must be signed in to change notification settings - Fork 9
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
incorrectly branching into cheatcode call during cse summarization #822
Comments
This is strange, because (I think) this means that |
@PetarMax I don't have this constraint. Here's the full conf of node 5 (cropping some parts for brevity):
|
Ok, thank you, could you please give me the configuration of node 6 as well? |
is there, which should prevent the branching... |
@palinatolmach When summarising a function, if one of the parameters is an address, I think that we need to assume that it does not equal the cheatcode account address. |
Agreed @PetarMax, I'll open an issue and a PR for it later today. Should we do it for an |
Both, I think. |
Thanks! Opened and assigned myself: #827. |
When applying cse kontrol produces a
#cheatcode_call
branch due to a possible misinterpretation of a symoblic variable when applying#checkCall
.To reproduce, perform the following, using kontrol 1.0.25
src
and theuniswapV2SwapTest
was undertest
forge test
andkontrol build
uniswapV2Pair.sync()
function so runkontrol prove --match-test 'uniswapV2Pair.sync()' --break-on-calls --cse
Should fail as follows:
kontrol show 'uniswapV2Pair.sync()'
Following is the related part from kcfg
The text was updated successfully, but these errors were encountered: