#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):

 Isn't it telling you?
 {{{
 ==13541==    by 0x2239B64D:
 
__pyx_f_4sage_4libs_8singular_8function_call_function(__pyx_obj_4sage_4libs_8singular_8function_SingularFunction*,
 _object*, _object*,
 
__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)
 }}}
 You should be able to look that line up: `(function.cpp:11924)`. I suppose
 that's a cython generated file, so the context there will tell you which
 function this is in the corresponding `function.pyx` file.

 I have no experience with valgrind myself. However, I think Python's
 memory management can confuse valgrind quite a bit. I was actually more
 hoping for a "double free" or "access to freed memory block" type error
 (i.e., illegal use of a pointer value.)

 It may well be that my SIGILL is indeed a matter of mpfr on Corei7
 compiling to something that's too fancy for valgrind and not a pointer to
 an error.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11918#comment:11>
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.

Reply via email to