#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:39 SimonKing]:
 > I've put the following two files into the `patches/` folder of the
 singular-3-1-5.malloc-linux spkg:
 [...]

 Perhaps backport this instead (should be pretty straightforward to replace
 the patches):

 [http://www.singular.uni-kl.de:8002/trac/changeset/15435]

 It looks like the second issue is also addressed. Are the other issues
 within your reach to investigate? I'm not really comfortable tracing
 through templated C++.

 The FC16 packaged valgrind didn't work for me due to unsupported machine
 instructions, but the latest valgrind release fixes that and installing
 that in /usr/local was a breeze! I can thoroughly recommend using it. The
 information it gives seem spot-on.
 (I was able to diagnose both these issues by just looking at the valgrind
 report and tracing through the code from allocation to access error. It
 won't always be that straightforward, but one can hope)

 With

 [http://sage.math.washington.edu/home/nbruin/sage.supp]

 the amount of false (or at least for me uninteresting) reports is
 bearable.

 It's unlikely, but the errors we've found could lead to random corruptions
 and hence explain the peculiar system-dependent bugs we've experienced.

 I'm afraid we're not done yet, though: Although we haven't found a GC
 mismatch here, we're pretty sure they exist. Also these corruptions should
 cause bad problems all around, not just after introducing GC.

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