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

 Replying to [comment:41 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]

 Yes, that looks like the right thing to do.

 My plan is to take your Singular-malloc spkg and turn it into a "proper"
 spkg, in the sense that the changes that you did to the source code will
 become patches that are ''optionally'' applied (say, if one does `export
 SAGE_SINGULA_MALLOC=yes`).

 The backported fix will of course be an unconditional patch.

 > 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++.

 Neither am I. But at least (in contrast to me!) you are comfortable to
 work with valgrind! Perhaps you could open a ticket to make your `.supp`
 file available to people? After all, there is a totally outdated valgrind
 spkg...

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