-
Notifications
You must be signed in to change notification settings - Fork 76
Exact Fractional Solver SegFaults #110
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
Comments
Can you build in debug mode to see if an assert comes up? (And post the log file.) |
I assume by log you mean the I got the logs with the commands:
out_standard.log The assertion error is:
|
Great, do you have experience to run this in a debugger and print the backtrace and the values in the assert (boundtype, newbound, oldlb)? |
I get the following backtrace:
and when using
I assume the values are:
|
I guess it is failing because And it is asserted that |
Suspicious that the backtrace does not show any exact function, especially I wonder why |
Unfortunately, I think the commit (820c627) of the version of SCIP that I used back then has been squashed. I updated the version of SCIP to the master ever since and could not reproduce the error. Though, the formulation seems to be particularly problematic. The not exact version solves the formulation in few milliseconds, the exact version does not seem to want to finish. Not sure if this is normal and warrants an issue. |
Nvm, the commit is there... |
The assertion fail is still reproducible on latest |
Oh, yeah, I tested in release... Ops |
Version:
The formulation in question
formulation.lp (Uploaded as TXT because GitHub complains)
The formulation solves fine when not using exact fractional, but seg-faults when using the exact fractional solver.
The text was updated successfully, but these errors were encountered: