On Fri, Jul 30, 2010 at 1:44 AM, Mitesh Patel <qed...@gmail.com> wrote: > On 07/30/2010 01:54 AM, Craig Citro wrote: >> So we're currently working on a long-overdue release of Cython with >> all kinds of snazzy new features. However, our automated testing >> system seems to keep turning up sporadic segfaults when running the >> sage doctest suite. This is obviously bad, but we're having a hard >> time reproducing this -- they seem to be *very* occasional failures >> while starting up sage, and thus far the only consistent appearance >> has been *within* our automated testing system (hudson). We've got a >> pile of dumped cores, which have mostly led us to the conclusions that >> (1) the problem occurs at a seemingly random point, so we should >> suspect some sort of memory corruption, and (2) sage does a *whole* >> lot of stuff when it starts up. ;) >> >> So we'd love to see if other people see these same failures. Anyone >> want to try out the new cython? You can grab all the files you need >> here: >> >> http://sage.math.washington.edu/home/craigcitro/cython-0.13-beta/ >> >> There's a new spkg and 6 patches against the sage library. You can add >> the patches, sage -i the spkg, and then do a sage -ba, and voila! you >> should have a sage running the bleeding edge cython. (If that doesn't >> build, it means I forgot some patch somewhere -- there's a working >> sage-4.4.4 with the new cython in /scratch/craigcitro/cy-work/fcubed >> on sage.math if anyone wants to root around.) > > I haven't done any testing yet, but in order to get './sage -ba' to > finish, I applied a seventh patch (attached), which I discovered with > > hg diff -R /scratch/craigcitro/cy-work/fcubed/devel/sage
Thanks! Yes, you'd probably need that too. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
