-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
par-or tactic triggers a segmentation fault #6500
Comments
Backtrace with symbols:
Version: e423fab |
I can't repro it easily, but it has to be that one solver finished and canceled the other that just was retrieving a model. Then as it was canceled it returned the null model. I will later push a fix that checks for the null model to avoid the crash and you can see if it helps. |
Signed-off-by: Nikolaj Bjorner <nbjorner@microsoft.com>
Sounds good. Thanks. |
I tested the fix with the script above and more examples and the issue didn't show up again. The fix seems to work fine. Thanks! |
Signed-off-by: Nikolaj Bjorner <nbjorner@microsoft.com>
Consider this SMTLIB script: game.lus.contractck.4.txt
Most of the time z3 runs OK on the file, but sometimes z3 triggers a segmentation fault. Here is the backtrace I got with GDB:
The issue seems to happen only when the
par-or
tactic is used. Using only eitherqe
orqe2
instead of thepar-or
tactic works fine.The text was updated successfully, but these errors were encountered: