Regarding the over-marking in overmark.c of tracer-x/klee-examples#136. This is caused by marking in a common parent of a constraint in the path condition, which is not used in one of the children, causing unnecessarily strong stored interpolant.
Credits to @rasoolmaghareh for discovering this issue, and to Joxan Jaffar for discussions.
Note this issue was resolved in TRACER by having separate markings for the children in a branch of the execution tree.
Regarding the over-marking in
overmark.c
of tracer-x/klee-examples#136. This is caused by marking in a common parent of a constraint in the path condition, which is not used in one of the children, causing unnecessarily strong stored interpolant.Credits to @rasoolmaghareh for discovering this issue, and to Joxan Jaffar for discussions.
Note this issue was resolved in TRACER by having separate markings for the children in a branch of the execution tree.