runtimeverification / runtimeverification/haskell-backend
kore-repl finds \not\ceil in stuck state
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
While testing an evm proof in the kore-repl in evm-semantics[1], kore-repl reported the following error:
kore-repl: [1188273727] Error (ErrorException):
Found '\not(\ceil(_))' in stuck configuration:
.... (long kore output)
This happened twice in the debugger when running stepf 2000 on the claim in question.
Full output: notceilbug-output.txt
To reproduce:
evm-semantics $ git checkout df290c1a # tag jb/bug-not-ceil
evm-semantics $ make tests/specs/mcd/verification/haskell/timestamp
evm-semantics $ kevm prove scratch/flopper-file-ttl-tau.k --backend haskell --format-failures --definition tests/specs/mcd/verification/haskell --debugger
Welcome to the Kore Repl! Use 'help' to get started.
Kore (0)> stepf 2000
kore-repl: [1188273727] Error (ErrorException):
Found '\not(\ceil(_))' in stuck configuration:
(occurring twice within the 2000 steps)
[1] Repo state tagged, https://github.com/runtimeverification/evm-semantics/tree/jb/bug-not-ceil
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking out evm-semantics at df290c1a, building tests/specs/mcd/verification/haskell/timestamp, and running the documented kevm prove command with --debugger. Use stepf 2000 to reproduce the stuck configuration and compare it with notceilbug-output.txt; done means the repeated \not(\ceil(_)) error no longer occurs during this run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100