[K-Bug] kprove generates kore claims that do not correspond to the K version

Open
#4,291 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
compilers

Research direction

Reproduce the issue with kompile a.k --backend haskell && kprove spec.k, using the supplied a.k and spec.k definitions. Inspect the generated Kore claim and its RHS sort; done means the claim is rejected as invalid or kprove proves it without producing a term outside MyList.

Written by the indexing model from the issue text.

Description

What component is the issue in?

None

Which command
  • kompile
  • kast
  • krun
  • kprove
  • kprovex
  • ksearch
What K Version?

v6.3.45-0-g736e297aa9-dirty

Operating System

Linux

K Definitions (If Possible)

a.k:

module A
  imports BOOL
  imports BYTES
  imports INT

  syntax MyList ::= List{Int, ""}

  syntax A ::= a(KItem) | b(KItem)
  rule a(_:Int L:MyList) => b(L)

endmodule

spec.k:

module SPEC
  imports A

  claim <k> a(1 2) => b(2:MyList) ... </k>
endmodule
Steps to Reproduce
kompile a.k --backend haskell && kprove spec.k

Note that the Kore RHS of the claim contains this subterm, which has nothing of sort MyList as specified in the claim.

                            Lblb'LParUndsRParUnds'A'Unds'A'Unds'KItem{}(
                                inj{SortInt{}, SortKItem{}}(
                                    \dv{SortInt{}}("2")
                                )
                            )
Expected Results

Either there should be an error in the claim file, or kprove should prove the claim.

Dominant language
Python
Stars
591
Forks
163
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from runtimeverification/k

All issues in runtimeverification/k

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.