Open rainoftime opened 3 years ago
Just to speed things along: how did you configure Boolector? What SAT solvers did you enable?
Why am I asking? Well, this could be an uninitialised read inside of the Boolector code, or it could be an an uninitialised read inside one of Boolector's dependancies.
For me, with a build that only uses Lingeling, I cannot reproduce this issue.
I re-build boolector with lingeling (there is only lingeling
in boolector\dep
./configure.sh -g --asan
-- Found PythonInterp: /usr/bin/python (found version "2.7.12")
-- Build type: Debug
-- Shared build: yes
-- ASAN support: yes
-- UBSAN support: no
-- Assertions enabled: no
-- gcov support: no
-- gprof support: no
-- Logging support: yes
-- Python bindings: no
-- Time statistics: yes
-- CaDiCaL: yes
-- CryptoMiniSat: yes
-- Lingeling: yes
-- MiniSat: yes
-- PicoSAT: yes
-- GMP: no
The error info seems different
boolector: /boolector/src/btorslvquant.c:1054: refine_exists_solver: Assertion `res != e_solver->true_exp' failed.
[btor>main] CAUGHT SIGNAL 6
unknown
xargs: /boolector: terminated by signal 6
(set-logic BV)
(declare-fun _substvar_111_ () Bool)
(declare-const v2 Bool)
(declare-const v5 Bool)
(declare-const v6 Bool)
(declare-const bv_2-1 (_ BitVec 2))
(declare-const v39 Bool)
(assert (not (exists ((q0 Bool)) (or (not (or q0 q0 v6 v2 q0 q0 q0)) _substvar_111_ v5))))
(check-sat)
Hi, for the following formula, boolector 6fce0ac