#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 SimonKing):
Replying to [comment:28 nbruin]:
> That all should be safe.
... which is bad, because I need someone that I can blame }:->
> I suppose the corruption happens somewhere lower down. Incidentally, the
valgrind report points to ''exactly'' those two snippets. So valgrind
reporting for these things is really very good.
It is not clear to me what you mean by "those two snippets": The
definition of `omEmulateAlloc0`, or the snippets that I provided in my
previous post?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13731#comment:29>
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.
