#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:82 SimonKing]:
> Nils, do you know how to do those things?
No, I don't, but it looks like you're learning how to on libsingular-devel
already. The `xalloc` approach seems to be what I was contemplating before
I read up on `malloc_size` and `malloc_usable_size`. It's interesting to
see that the singular people thought it was easier to write a wrapper from
scratch than to amend `omalloc`. I can sympathize with that, although it
wasn't so bad in the end.
If xalloc does result in a usable executable, that would be great! I
wonder what prevents us from getting that.
It may be that once you've built xalloc.so, you can just do
`LD_PRELOAD=xalloc.so` to pre-empt the normal omalloc routines. That's how
things like `ElectricFence` capture malloc action (provided omalloc
doesn't get statically linked)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13731#comment:83>
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.
