On Monday, November 19, 2012 4:06:18 PM UTC+1, Jean-Pierre Flori wrote: > > > > On Monday, November 19, 2012 4:03:21 PM UTC+1, Jean-Pierre Flori wrote: >> >> >> On Saturday, November 17, 2012 9:05:11 AM UTC+1, Nils Bruin wrote: >>> >>> It's worth running the sage testsuite on linux with "export >>> MALLOC_CHECK_=3" (on OSX, look up gmalloc for similar testing). It >>> makes malloc a little less tolerant of misuse. It found a problem in >>> graph_generators.py. See >>> >>> http://trac.sagemath.org/sage_trac/ticket/13719 >>> >> >> Using the same settings, I got the same segfauilt and a SIGABORT in >> polynomial/pbori.pyx. >> This was on sage 5.5.rc0 plus additional fixes from #12215 for PARI >> unique instance deallocation and #12313 for polybori double free problem >> for ReductionStrategies. >> > > The SIGABORT in pbori.pyx seems to come from the fix from #12313, oops. > It turned out the patch I had on my computer was an old version which did not contain the pbori fix, but only added a garbage collection which triggered the bug. With a proper patch, the doctests are fine.
-- 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.
