#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):
Gosh, it is so frustrating to hunt that Heisenbug!!
* Test the file - there is a segfault, but it doesn't give any clue of
what is happening.
* Test the file with gdb - the segfault is gone, but a "normal" error
occurs, that is rather odd because it is reported in the wrong line of the
file.
* Try ulimit -c unlimited - there is a segfault, but no core dump is
written.
* Try verbose tests - all tests pass.
* What I just did: Start each test with a few lines that write something
into a log file. Hence, it isn't exactly verbose, but should give some
idea in what test the segfault occurs. But alas - all tests pass.
* Valgrind doesn't seem to be available on bsd.math,
Anything else I could try? So far, I only see the option to try to
understand why using gdb results in an error in a very innocent-looking
test that should actually use a strong cache.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:240>
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.
