#11339: Illegal use of __deallocate__ in cython (pyx) code
-----------------------------------------------+----------------------------
Reporter: gagern | Owner: drkirkby
Type: defect | Status: needs_info
Priority: major | Milestone: sage-4.7.1
Component: algebra | Keywords: sd31
Work_issues: | Upstream: N/A
Reviewer: François Bissey, Steven Trogdon | Author: Volker Braun,
Martin von Gagern
Merged: | Dependencies:
-----------------------------------------------+----------------------------
Changes (by vbraun):
* status: needs_review => needs_info
Comment:
I had similar problems, but I thought I fixed them and it did pass tests
on my machine. In my experience, they always go away if we leak the ring
(which is essentially what we did before) instead of cleaning up after we
are done with it. I have a suspicion that, although almost all take a ring
as argument, some Singular functions require `currRing` to be set. This is
why I added the inlined `_check_ring()` function to each
`MPolynomial_libsingular` method to make sure that we have the right
`currRing`.
I've added a superfluous `p_Normalize` call to
`MPolynomial_libsingular.__dealloc__`, this is likely the point where you
are crashing. You'll get a more useful backtrace if you paste the
offending doctest into `sage -gdb` and then use "bt".
Maybe somebody who is more familiar with the Singular api can chime in and
explain precisely where you have to call `rChangeCurrRing` and where you
don't need to.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11339#comment:27>
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.
