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
polybori crash (Linux) #12654
Comments
Minimal Input that makes polybori crash |
Attachment: ticketMinimal.sage.gz Output of the test file |
Attachment: testOut.txt Attachment: testError.txt Error message of the test file |
Upstream: Fixed upstream, in a later stable release. |
Changed keywords from polibori multivariate quadratic polynomials to polybori multivariate quadratic polynomials |
comment:2
Replying to @alexanderdreyer:
Maybe #11575 already fixed that (still it works only for sage-5.0). |
comment:3
Thanks for pointing this out! Yes, the bug is gone with sage-5.0beta_a11. Best, |
comment:4
Duplicate of #11575. |
This comment has been minimized.
This comment has been minimized.
comment:5
Abusing "positive review", because I cannot close it. |
comment:6
In such cases, you should set the milestone to "sage-duplicate/invalid/wontfix". |
Reviewer: Alexander Dreyer |
Hello,
I think I found a bug in Sage 4.8, more specifically in polybori. Polybori terminates with a "segmentation fault". I have attached the input (sparse polynomials) and the output. I can reproduce the error with this specific input.
For smaller instances (i.e. less variables, less equations), the programme runs fine and the output is correct.
The machine has about 256 GB RAM, uses an AMD Opteron(TM) Processor 6276 @ 2.3 GHz and runs under Linux 2.6.32-220.2.1.el6.x86_64.
If you need any more info: Please drop me a line!
Best,
Christopher
Duplicate of #11575.
Upstream: Fixed upstream, in a later stable release.
CC: @alexanderdreyer
Component: packages: standard
Keywords: polybori multivariate quadratic polynomials
Reviewer: Alexander Dreyer
Issue created by migration from https://trac.sagemath.org/ticket/12654
The text was updated successfully, but these errors were encountered: