#4934: [with patch; needs review] matrix1.pyx refernece related doctest crash on
cicero
----------------------+-----------------------------------------------------
Reporter: mabshoff | Owner: robertwb
Type: defect | Status: new
Priority: blocker | Milestone: sage-3.2.3
Component: doctest | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Changes (by was):
* summary: matrix1.pyx refernece related doctest crash on cicero =>
[with patch; needs review] matrix1.pyx
refernece related doctest crash on cicero
Comment:
Some debugging info:
{{{
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 also found a way to stop the problem. I think this is just programming
around a bug in Cython though. Hopefully the fact that the attached
patch stops the will help Robert Bradshaw find the true source of the
problem (which I suspect to be a Cython bug).
Anyway, applying the attached patch would at least make it so we can
release sage-3.2.3. If this is done, though, then another ticket must be
opened to fix whatever cython bug (I maintain) caused this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4934#comment:1>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
