On Wednesday, December 19, 2012 11:16:50 AM UTC+1, Jeroen Demeyer wrote: > > Just when I thought the #715 + #11521 issues were fixed in sage-5.5.rc1... > > Apparently, sage-5.6.beta0 has uncovered a new problem: with the current > sage-5.6.beta0, I get the following reproducible segfault on hawk > (OpenSolaris i386): > > > sage -t --long -force_lib devel/sage/sage/modules/module.pyx > > The doctested process was killed by signal 11 > > [24.3 s] > > More details are available somewhere? A gdb backtrace?
> Removing #8992 (the only ticket in sage-5.6.beta0 which seems remotely > related) doesn't help. Reverting #715, #11521, #13746 does fix it. Now I > don't know how to proceed, I am tempted to revert these tickets in the > sage-5.5 release. > > Jeroen. > -- 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.
