On Sun, Jan 4, 2009 at 9:17 PM, mabshoff <mabsh...@googlemail.com> wrote: > Cool. The dirty fix is to disable that doctest for now. If I ran the
That is very dirty indeed. I think I prefer at least the hack I've posted to the ticket, which is to make the variable public. > last doctest by itself it passed, running the whole doctest crashed > valgrind 3.3.1. There is brand spanking new 3.4 release I have been > playing with for most of the day, but I haven't tried it. IIRC the > doctest valgrinds clean on sage.math. > > From http://www.python.org/download/releases/2.5.3/NEWS.txt > > - Issue #3100: Corrected a crash on deallocation of a subclassed > weakref which > holds the last (strong) reference to its referent. > > The above issue could be partially responsible for what we are seeing, > but given the number of times making something no longer weekly > referenced fixing mysterious errors I could see this being involved in > some cases. Yes, I claimed a possible bug in Cython a few times on the ticket, but you're right, this could be an issue with Python. In any case, that changing the variable to be public makes the problem go away must be a hint. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
