On Tuesday, December 25, 2012 1:44:01 AM UTC+1, Jean-Pierre Flori wrote: > > > > On Monday, December 24, 2012 11:18:26 PM UTC+1, Jean-Pierre Flori wrote: >> >> >> >> On Monday, December 24, 2012 10:54:48 PM UTC+1, Simon King wrote: >>> >>> Hi Jean-Pierre, >>> >>> On 2012-12-24, Jean-Pierre Flori <jpf...@gmail.com> wrote: >>> > Not sure we got these so clearly before, but using --without-pymalloc >>> and >>> > Valgrind (hint: finish and review #13060) I get lots of >>> > >>> > >>> >==28631== Invalid read of size 8 >>> >==28631== at 0x10429E50: >>> > __pyx_tp_dealloc_4sage_9structure_15category_object_CategoryObject >>> > (category_object.c:8990) >>> > ... >>> >==28631== by 0x10A6CD28: >>> > __pyx_pw_4sage_9structure_11coerce_dict_16TripleDictEraser_3__call__ >>> > (coerce_dict.c:1225) >>> >>> OK, that's good, because it clearly points to the stuff from #715 and >>> thus gives hope to find a bug in the new code. >>> >> Yup, let's hope so. >> >> Maybe the problem is with endomorphism rings, because we have the domain >> and codomain pointing to the same parent, that's a nice culprit for a >> superfluous decref. >> > Any reason for calling directly _refcache.__delitem__ rather than del > _refcache ? > Changing this solves the problem, but surely only by hiding the bug... > Indeed, rebuilding everything with --with-pydebug is just scary. You get the smae failure as above, but everywhere (because asserts are checked and you don't have to pray for a segfault)
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. 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. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
