#9389: Bug in polynomials over residue fields (was: sage crashing when computing
local_data() for an EC)
-----------------------------+----------------------------------------------
Reporter: arminstraub | Owner: davidloeffler
Type: defect | Status: new
Priority: major | Milestone:
Component: number fields | Keywords: segfault polynomial finite field
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by ylchapuy):
as a simple workaround, this solves the problem:
{{{
diff -r 1b5dc2667b48 sage/rings/polynomial/polynomial_ring.py
--- a/sage/rings/polynomial/polynomial_ring.py Sat Oct 23 15:07:20 2010
+0200
+++ b/sage/rings/polynomial/polynomial_ring.py Thu Oct 28 15:53:58 2010
+0200
@@ -1222,7 +1222,7 @@
"""
if implementation is None: implementation="NTL"
from sage.rings.finite_rings.finite_field_base import
is_FiniteField
- if implementation == "NTL" and is_FiniteField(base_ring):
+ if implementation == "NTL" and is_FiniteField(base_ring) and not
isinstance(base_ring, sage.rings.residue_field.ResidueField_generic):
p=base_ring.characteristic()
from sage.libs.ntl.ntl_ZZ_pEContext import ntl_ZZ_pEContext
from sage.libs.ntl.ntl_ZZ_pX import ntl_ZZ_pX
}}}
Though I must admit I don't know which difference between GF(4) and
K.ideal(2).residue_field() makes everything go boom here.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9389#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.
