#715: Parents probably not reclaimed due to too much caching
-------------------------------------------------------------------+--------
       Reporter:  robertwb                                         |         
Owner:  somebody                                 
           Type:  defect                                           |        
Status:  needs_review                             
       Priority:  major                                            |     
Milestone:  sage-5.4                                 
      Component:  coercion                                         |    
Resolution:                                           
       Keywords:  weak cache coercion Cernay2012                   |   Work 
issues:                                           
Report Upstream:  N/A                                              |     
Reviewers:  Jean-Pierre Flori, Simon King, Nils Bruin
        Authors:  Simon King, Jean-Pierre Flori                    |     Merged 
in:                                           
   Dependencies:  #9138, #11900, #11599, to be merged with #11521  |      
Stopgaps:                                           
-------------------------------------------------------------------+--------

Comment (by SimonKing):

 With [attachment:cachefunc_94107.py], I get:
 {{{
 (sage-sh) SimonKing@bsd:sage$ python -t
 ~/SAGE/work/signal11/cachefunc_94107.py

 ------------------------------------------------------------------------
 Unhandled SIGSEGV: A segmentation fault occurred in Sage.
 This probably occurred because a *compiled* component of Sage has a bug
 in it and is not properly wrapped with sig_on(), sig_off(). You might
 want to run Sage under gdb with 'sage -gdb' to debug this.
 Sage will now terminate.
 ------------------------------------------------------------------------
 Segmentation fault
 }}}

 So, that looks much more expressive than what sage -t reports!

 However, setting ulimit -c unlimited did not result in a dumped core:
 {{{
 (sage-sh) SimonKing@bsd:sage$ ulimit -c unlimited
 (sage-sh) SimonKing@bsd:sage$ python -t
 ~/SAGE/work/signal11/cachefunc_94107.py
 ...
 Segmentation fault
 (sage-sh) SimonKing@bsd:sage$ ls /cores/
 (sage-sh) SimonKing@bsd:sage$
 }}}

 So, can you explain how I could get a core dump?

 Apply trac_715_combined.patch trac_715_local_refcache.patch
 trac_715_safer.patch trac_715_specification.patch

 And then #11521

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