Closed quickbeam123 closed 11 months ago
This could be fixed already in the latest version of z3 (a reason to jump forward). If not, we should probably turn this into a MWE and file a ticket with them...
I think we're already on the last release (4.12.2) of Z3. I can reproduce the bug, but exporting the log and running the Z3 binary on it says "sat" quite happily. :-/
Thank you for trying this out, Michael!
I once had a tiny cpp stub program interfacing the z3 api directly and issuing just the necessary calls. I will check out if I can revive it.
Regarding releases, we could also jump to an arbitrary (non-release) commit, but maybe that's not such a great idea...
The issue looks like this:
on 44.txt