#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 SimonKing):
Hi Nils,
thank you for the sage.supp at #11918! When I run the tests of
sage/rings/polynomial/infinite_polynomial_ring.py (which make Volker's
patchbot at #12876 segfault, even though they are fine for me, I do not
get a SIGILL. But I do get a considerable amount of lost memory:
{{{
==13541== 13,936 bytes in 1 blocks are definitely lost in loss record
8,673 of 8,997
==13541== at 0x4C244E8: malloc (vg_replace_malloc.c:236)
==13541== by 0x21E8984F: omAllocFromSystem (omAllocSystem.c:184)
==13541== by 0x21E89A21: omAllocLarge (omAllocSystem.c:39)
==13541== by 0x21BB3A00: iiAllStart(procinfo*, char*, feBufferTypes,
int) (omalloc.h:2432)
==13541== by 0x21BB3B95: iiPStart(idrec*, sleftv*) (iplib.cc:360)
==13541== by 0x21BB4148: iiMake_proc(idrec*, sip_package*, sleftv*)
(iplib.cc:482)
==13541== by 0x2239B64D:
__pyx_f_4sage_4libs_8singular_8function_call_function(__pyx_obj_4sage_4libs_8singular_8function_SingularFunction*,
_object*, _object*, __pyx_opt_args_4sage_4libs_8singular_8f
unction_call_function*) (function.cpp:13241)
==13541== by 0x2239CBA8:
__pyx_pw_4sage_4libs_8singular_8function_16SingularFunction_5__call__(_object*,
_object*, _object*) (function.cpp:11924)
==13541== by 0x4E742C2: PyObject_Call (abstract.c:2529)
==13541== by 0x4F160FC: PyEval_EvalFrameEx (ceval.c:4239)
==13541== by 0x4F19124: PyEval_EvalCodeEx (ceval.c:3253)
==13541== by 0x4E9C122: function_call (funcobject.c:526)
==13541== by 0x4E742C2: PyObject_Call (abstract.c:2529)
==13541== by 0x4F14C59: PyEval_EvalFrameEx (ceval.c:4334)
==13541== by 0x4F19124: PyEval_EvalCodeEx (ceval.c:3253)
==13541== by 0x4E9C122: function_call (funcobject.c:526)
==13541== by 0x4E742C2: PyObject_Call (abstract.c:2529)
==13541== by 0x4F14C59: PyEval_EvalFrameEx (ceval.c:4334)
==13541== by 0x4F19124: PyEval_EvalCodeEx (ceval.c:3253)
==13541== by 0x4E9C122: function_call (funcobject.c:526)
==13541== by 0x4E742C2: PyObject_Call (abstract.c:2529)
==13541== by 0xB29B841:
__pyx_pw_4sage_4misc_9cachefunc_12CachedMethod_3_instance_call
(cachefunc.c:9733)
==13541== by 0x4E742C2: PyObject_Call (abstract.c:2529)
==13541== by 0xB29C7D4:
__pyx_pw_4sage_4misc_9cachefunc_18CachedMethodCaller_7__call__
(cachefunc.c:7254)
==13541== by 0x4E742C2: PyObject_Call (abstract.c:2529)
}}}
Is there a way to find out what singular_function or what cached method
are involved?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11918#comment:10>
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.
