-
Notifications
You must be signed in to change notification settings - Fork 5
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
Unigen crashes on a benchmark. #13
Comments
Hi, Thanks for the bugreport! Unfortunately, I cannot reproduce this bug. I have added some minor changes, to make sure we catch something like this, but I can't seem to reproduce it. Can you please give me the full output of your
please? Also, unfortunately the above will not give the Arjun version (which I have now fixed). In general, I think you need to update CryptoMiniSat, Arjun, ApproxMC, and UniGen, i.e. ALL of them, in that order, and then the bug will be gone. Can you please check if the bug goes away if you do that? Thanks, Mate |
For me, the
By the way, next time you need to paste such text in, you can use the triple-backtick at the beginning of the text, and then the triple-backtick at the end of your text. I fixed your bugreport to use this. It looks better and is a lot less work in general. Please check how I fixed it and next time you can use the triple-backtick so it's easier for both you and me. Thanks! Mate |
I am still getting the same bug after updating. This is output of
I updated CryptoMiniSat, Arjun, ApproxMC, and UniGen in that order. The SHA revision values for CMS, Arjun, ApproxMC, and Unigen are of the latest commits as of now. |
Ah, I see, I can now reproduce it. Sorry, let me look at this. |
I have managed to find the issue. Can you please test and if it's good, close this issue? Thanks! You will need to update CMS, Arjun, ApproxMC, and UniGen. Sorry, it wasn't my idea to cut it into so many projects :S Let me know if this fixed it, Mate |
Works perfectly! Thank you. |
I ran the following command:
./unigen --seed 1023 -v 0 bug.txt
It gives me the output:
However, I did not get the error for a different seed:
./unigen --seed 1024 -v 0 bug.txt
I have attached the buggy cnf. bug.txt
I suspect that the bug is in the maintenance of the sampling vars, as this line of the output seems to say that '0' is a sampling var.
c [unig] Original sampling vars: 31 0 1 2 3 4 5 6 33 32 20 21 22 23 24 25 26 27 28 29 30
The text was updated successfully, but these errors were encountered: