#11918: Sage should ship its Valgrind suppressions file, or not insist on its
presence
----------------------------------------------------------------+-----------
Reporter: leif |
Owner: tbd
Type: defect |
Status: new
Priority: major |
Milestone: sage-5.3
Component: scripts |
Resolution:
Keywords: --valgrind --memcheck sage.supp suppressions | Work
issues:
Report Upstream: N/A |
Reviewers:
Authors: | Merged
in:
Dependencies: |
Stopgaps:
----------------------------------------------------------------+-----------
Comment (by nbruin):
Replying to [comment:12 SimonKing]:
> Replying to [comment:11 nbruin]:
> > Isn't it telling you?
>
> No, it isn't. It just tells that it is a singular_function (as defined
in sage.libs.singular.function), but it could be any function of Singular
(std, slimgb, reduce, system, ...)
Oh, right. That's going to just as opaque as debugging python code with
gdb then. I guess you could try and set a breakpoint at the function and
then investigate the arguments? It's triggering `iiPStart` though. That
might tell you something?
Anyway, given that there's a good chance this is a false positive anyway,
perhaps this call sequence might not be the one to concentrate on. I'd
imagine `omalloc` plays tricks that would confuse valgrind (it's an
advanced memory manager after all!), so `malloc` "losing" memory doesn't
sound particularly worrisome to me.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11918#comment:13>
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.
