#7795: MPolynomialRing segfaults when getting high exponents
----------------------------------------------------------------------------+
Reporter: SimonKing |
Owner: malb
Type: defect |
Status: positive_review
Priority: major |
Milestone: sage-duplicate/invalid/wontfix
Component: commutative algebra |
Resolution:
Keywords: MPolynomialRing_libsingular segfault with high exponents |
Work issues:
Report Upstream: Completely fixed; Fix reported upstream |
Reviewers: Charles Bouillaguet
Authors: |
Merged in:
Dependencies: |
Stopgaps:
----------------------------------------------------------------------------+
Comment (by SimonKing):
Replying to [comment:13 Bouillaguet]:
> This cannot possibly be doctested, so we might as well close this.
I disagree, in two regards.
First of all, if no error is raised and no crash occurs, then apparently
the example is different. Could be a 32-bit versus 64-bit problem. Or not?
I don't think that the problem I originally reported was 32 bit.
So, one should try to find an example in which a segfault used to occur,
but an error is raised now. Can someone please test whether the following
segfaults with sage-4.3?
{{{
sage: F.<a> = FiniteField(3)
sage: P.<T,z> = PolynomialRing(F)
sage: (T+z)^(5^15)
Traceback (most recent call last):
...
OverflowError: Exponent overflow (30517578125).
}}}
If that test segfaults in old Sage versions, then it is a valid test (in
particular, those types of bugs ''can'' be tested against).
So, who has old Sage versions hanging around?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7795#comment:15>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
