#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 pcpa):
Replying to [comment:5 nbruin]:
> Replying to [comment:4 pcpa]:
> > I do not see this in my current sagemath-5.4 rpm package
> Thanks for checking!
>
> Are you sure your singular gets built to use the glibc malloc for all
small allocations and not omalloc on "malloc"-ed pages? You may try
setting `EXTRA=0` to remove the padding. I don't expect that padding comes
into play, though. I suspect a double free or a free on a pointer that
doesn't point to a malloc-ed block to begin with.
Sorry, I completely misunderstood what was mean't by the spkg and the
'--with-emulate-omalloc' option. I will try to debug more later, but I
cannot build the Singular rpm with that option as it always fails in the
kernel subdirectory due to missing omEmulate* declarations.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13731#comment:6>
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.
