On Sun, Jan 4, 2009 at 9:01 PM, William Stein <wst...@gmail.com> wrote: > On Fri, Jan 2, 2009 at 11:32 PM, mabshoff <mabsh...@googlemail.com> wrote: >> >> Hello folks, >> >> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list. >> Well, technically the following happened: the first final had some >> issues, so it was renamed rc0 and a new final was spun with a number >> of fixes. >> >> Most of the fixes are stabilization and bug fixes only in nature, so >> this release should be rather solid. It seems that things were rather >> quiet over the last couple days, but I guess that also has its good >> sides :) This release should be next to identical to 3.2.3 unless >> something major pops up. > > Your ticket #4934 segfault: > > http://trac.sagemath.org/sage_trac/ticket/4934 > > which you were just seeing on cicero is popping up for me on several test > os's on several compilers. > > I'm getting exactly this test failure in "make check" on debian 32 and > 64-bit vanilla (with gcc-4.1.2) under vmware with 1GB RAM and also the > same failure on 32-bit Ubuntu 1GB RAM (with gcc-4.3.2): > > sage -t "devel/sage/sage/matrix/matrix1.pyx" > A mysterious error (perphaps a memory error?) occurred, which may have > crashed doctest. > [4.3 s] > > If I do --verbose I get: > > Trying: > a._mathematica_init_()###line 171:_sage_ >>> a._mathematica_init_() > Expecting: > '{{Pi, Sin[x]}, {Cos[x], (E) ^ (-1)}}' > ok > ------------------------------------------------------------ > 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). > ------------------------------------------------------------ > [4.9 s] > exit code: 1024 > > ============================ > > Under gdb, I get: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb7d5c8c0 (LWP 19059)] > 0xb2d53673 in > __pyx_tp_dealloc_4sage_6matrix_21matrix_symbolic_dense_Matrix_symbolic_dense > (o=0xb57a65c) at sage/matrix/matrix_symbolic_dense.c:6535 > 6535 Py_XDECREF(p->__variables); > (gdb) bt > #0 0xb2d53673 in > __pyx_tp_dealloc_4sage_6matrix_21matrix_symbolic_dense_Matrix_symbolic_dense > (o=0xb57a65c) at sage/matrix/matrix_symbolic_dense.c:6535 > #1 0x0808a1fc in PyDict_Clear (op=0xb3e713c) at Objects/dictobject.c:757 > ... > > ============================ > > > I'm going to look into this for a few minutes...
OK, I found a temporary workaround. See the patch at #4934. It would also be very nice if we could also fix the openSUSE build bug, since I think you said you know how (Michael Abshoff). I noticed that on both my 32 and 64-bit opensuse build machines, **************************************************** /bin/sh: symbol lookup error: /home/wstein/build/opensuse64/build/sage-3.2.3.final/local/lib/libreadline.so.5: undefined symbol: PC real 0m0.004s user 0m0.000s sys 0m0.004s sage: An error occurred while installing pari-2.3.3.p0 ... sh: symbol lookup error: /home/wstein/build/opensuse64/build/sage-3.2.3.final/local/lib/libreadline.so.5: undefined symbol: PC make: *** [check] Error 127 wst...@opensuse64:~/build/opensuse64/build/sage-3.2.3.final$ --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
