On Aug 30, 6:20 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
Hello David,
> On a suse 101. amd64: SAGE compiled file. The sage -testall
> revealed several seg faults, such as:
>
> sage -t matrix/strassen.pyx
I did valgrind that one on a 64 bit box, but didn't see anything
obvious.
>
> ------------------------------------------------------------
> 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.)
Could you do "sage -t -gdb devel/sage/sage/matrix/strassen.pyx"? Then
press "r" and once it crashes executed "bt" (for backtrace. That
requires gdb, but should give us a backtrace. If you need help I am in
#sage-devel.
> This also occurred in (in the source code section of
> the tests):
>
> sage -t modular/ssmod/ssmod.py
> sage -t modular/dirichlet.py
> sage -t rings/finite_field_element.py
>
I am testing those as I write this. You can do the same gdb thing as
above.
> and also (in the documentation section of the tests):
>
> sage -t tut.tex
>
> even though it said "All tests passed!" for that section.
>
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---
