Skip to content
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

Halmos thinks all paths will revert even though I can hardcode a counter example, due to loops #327

Open
GalloDaSballo opened this issue Jul 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@GalloDaSballo
Copy link

Describe the bug
I run

halmos --mc CryticTester

In this repo:
https://github.com/GalloDaSballo/halmos-loop-bug-repro

It fails with:

WARNING:Halmos:check_counter_symbolic(bytes4[],(uint256,address,address,uint256,uint256)[]): all paths have been reverted; the setup state or inputs may have been too restrictive.

I can run forge test --match-test test_counterSymbolic -vv

To reproduce a test that will pass, and doesn't revert

To Reproduce
Clone

https://github.com/GalloDaSballo/halmos-loop-bug-repro

Run

halmos --mc CryticTester

Environment:

  • MacOS
  • Python version: Python 2.7.16
  • halmos 0.1.13

Additional context

Running with

halmos --mc CryticTester --array-lengths selector=2,data=2 --loop 256 -vvvvv

Doesn't cause the message and instead allows Halmos to run the prover

@GalloDaSballo GalloDaSballo added the bug Something isn't working label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant