#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: Reported upstream. Developers acknowledge bug. |
Reviewers:
Authors: | Merged
in:
Dependencies: |
Stopgaps:
------------------------------------------------------------------+---------
Comment (by nbruin):
Replying to [comment:53 SimonKing]:
> > There's an option that selects whether omalloc should offer the
standard 'malloc/realloc/free' interface to its own allocators.
>
> What does that mean? If one uses omalloc, why should one ''not'' want
that it offers `malloc/realloc/free`?
It selects whether omalloc should offer its services ''under those
names'', i.e., as a drop-in replacement for the standard libc memory
manager. That's not what Singular does. It uses the various ''omalloc''
routines, which offer extra options. Otherwise, changing Singular would
have been a matter of "dropping out" the drop-in replacement. Instead we
have to jump through hoops to get omalloc to use libc's malloc (or
whatever drop-in replacement we want to use, like ElectricFence) behind
the scenes.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13731#comment:54>
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.
