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.

Sign up for GitHub

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

Jump to bottom

Misinterpretation of stuck result for #assume(false) as depth-bound(0) #3633

Closed
jberthold opened this issue Jul 31, 2023 · 2 comments
Closed

Misinterpretation of stuck result for #assume(false) as depth-bound(0) #3633

jberthold opened this issue Jul 31, 2023 · 2 comments

Comments

@jberthold
Copy link
Member

Related to #3630 and runtimeverification/evm-semantics#1944

It appears as though haskell-backend's kore-rpc returns depth-bound with depth: 0 in case an assume(false) is found in a foundry execution.
The expected result would be stuck, not depth-bound.
@ehildenb
Copy link
Member

We want a separate type of response though specifically, the vacuous response. See #3630.

@jberthold
Copy link
Member Author

The original problem is fixed in #3634 . If we want to add a new stop reason, we should discuss it on #3630 separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jberthold @ehildenb