#13731: Fix libsingular memory management
---------------------------+------------------------------------------------
Reporter: nbruin | Owner: rlm
Type: defect | Status: new
Priority: major | Milestone: sage-5.6
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
---------------------------+------------------------------------------------
Comment (by nbruin):
Replying to [comment:17 SimonKing]:
> How do I make it create a core dump, and how do I open it with gdb? I
recall something with "ulimit -c", but I can't recall the details...
I'd guess `ulimit -c unlimited`.
> `sage -gdb` does not work, by the way:
Yes, I had the same problem (and it's not singular-malloc's fault). It
seems to be a bad interaction between ipython and gdb. `sage -t -gdb` does
work, so I've just worked around it by wrapping it in a little test file:
`tester.py`:
{{{
def t():
r"""
sage: A.<x,y> = FreeAlgebra(QQ, 2)
sage: P.<x,y> = A.g_algebra({y*x:-x*y})
sage: x*y
"""
pass
}}}
Congratulations on getting my franken-spkg to build ...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13731#comment:18>
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.
