On 8/30/07, David Joyner <[EMAIL PROTECTED]> wrote: > > On a suse 101. amd64: SAGE compiled file. The sage -testall > revealed several seg faults, such as: > > sage -t matrix/strassen.pyx > > ------------------------------------------------------------ > Unhandled SIGSEGV: A segmentation fault occured in SAGE. > This probably occured because a *compiled* component > of SAGE has a bug in it (typically accessing invalid memory) > or is not properly wrapped with _sig_on, _sig_off. > You might want to run SAGE under gdb with 'sage -gdb' to debug this. > SAGE will now terminate (sorry). > ------------------------------------------------------------ > A mysterious error (perphaps a memory error?) occured, which may have > crashed doctest. > > (BTW, "occured" is spelled wrong I think.)
Thanks, I've fixed the spelling mistakes. The above crash looks pretty serious -- it's evidently a 64-bit only issue, which was probably introduced by our work to fix other bugs (??) and/or memory leaks. This will be a blocker that has to be fixed before sage-2.8.3 can be released. > sage -t tut.tex > > even though it said "All tests passed!" for that section. If one does "sage -testall" it also tests tut.tex and const.tex, I think, which is useful. The main thing I want though is the output of "make test". William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
