id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,work_issues,upstream,reviewer,author,merged,dependencies,stopgaps
11674,np.dot of two numeric matrices segfaults in the binary Ubuntu 10.04.1 x86_64 distribution,mister.wardrop,tbd,"Multiplying two ordinary matrices using numpy segfaults `sage`. Using a standard Python install, this does not happen.

Steps to reproduce:

 1. Run sage
 1. Run the following code:
{{{
#!python
import numpy as np
ms = np.load('matrices.npy')
np.dot(ms[0],ms[1])
}}}

Observe that Sage segfaults.

The actual segfault notification is: 
{{{
/PersonalStorage/Development/tools/sage/local/lib/libcsage.so(print_backtrace+0x31)[0x7f39008bd817]
/PersonalStorage/Development/tools/sage/local/lib/libcsage.so(sigdie+0x14)[0x7f39008bd849]
/PersonalStorage/Development/tools/sage/local/lib/libcsage.so(sage_signal_handler+0x20e)[0x7f39008bd474]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfc60)[0x7f39068d2c60]
/PersonalStorage/Development/tools/sage/local/lib/libatlas.so(+0x6b70d)[0x7f38fa76b70d]

----
Unhandled SIGSEGV: A segmentation fault occurred in Sage. This
probably occurred because a *compiled* component of Sage has a bug
in it and 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.
}}}

Running this code outside of Sage, in another python interpreter (with numpy 1.5.1) does not exhibit this fault.

For my work, this is debilitating; and I hope to publish a paper using these results soon.",defect,new,critical,sage-5.10,distribution,,ATLAS segfault matrix numpy libpthread redhawk,vbraun,,N/A,,,,,