#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: Fixed upstream, in a later stable release. | Reviewers:
Authors: Nils Bruin, Simon King | Merged in:
Dependencies: | Stopgaps:
--------------------------------------------------------------+-------------
Comment (by SimonKing):
Replying to [comment:114 nbruin]:
> I think running `sage -t --gdb ...` disables the timeout. If you're just
testing a single file you might as well do that (in `screen` of course--
it'll be a while before you check back). It's how I got thetraceback for
the first heisenbug. It also leaves you immediately with an environment
where you can examine the backtrace etc.
Well, I first wanted to have a "quick" overview: Is there any problematic
test? Namely, on Linux, everything works just fine with MALLOC_CHECK_
(except the known problem with the graphs). And ''if'' there is another
crash on OSX in the quick test then I wanted to analyse it more deeply.
But the only test that did not timeout with `SAGE_TIMEOUT=1800` was a test
that normally takes 3.5 seconds...
Is there any other memory checker than gmalloc that I can use on OSX, that
is faster and finds ''some'' of the issues that gmalloc would find?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13731#comment:115>
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.
