On Sun, May 16, 2010 at 05:55:10AM -0700, cschwan wrote: > Hello, > > porting Sage to Gentoo progresses well, we now have a "split" version > where all all dependencies of Sage are installed with portage. > Unfortunately, we experience serious problems on amd64 when exiting > Sage. When doing so, there is a slight chance of getting a SIGABRT > error, which is always looking like this one: > > sage -t -force_lib "devel/sage/doc/en/constructions/rings.rst" > *** glibc detected *** /usr/bin/python2.6: corrupted double-linked > list: 0x0000000004afc6e0 *** <snip> > followed by a memory dump which is aborted and the error message: The > doctested process was killed by signal 6 <snip>
> I have struggled with this error a long time and now I am running out > of ideas ... So these are my questions: > - Is this type of error known ? Has it already been fixed in Sage (I > know that the recent gcc-4.5 error look alike, but we are still using > gcc-4.3.4) ? > - If not, are there any ways to find out more about this error ? Did you try running it through valgrind? For memory errors like this that might give some more clues. 'sage -t' has a -valgrind option similar to -gdb that does this for you. -Willem Jan -- 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
