[SciPy-dev] Segmentation fault in symeig.test.test()

[Nils Wagner]

Pearu Peterson wrote:

>
>
> On Sat, 20 Nov 2004, Nils Wagner wrote:
>
>> Hi,
>>
>> I cannot resolve the problem with symeig.test.test() with respect to 
>> the symeig package.
>> http://mdp-toolkit.sourceforge.net/symeig.html
>>
>> A back trace yields
>>
>> (no debugging symbols found)...>>> symeig.test.test()
>> Random Seed:  (1268049219, 2102953867)
>> testComplex (symeig.test.test_symeig.SymeigTestCase) ...
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 1077041376 (LWP 16623)]
>> 0x411c1960 in ATL_cdotc_xp0yp0aXbX () from 
>> /usr/lib/python2.3/site-packages/symeig/froutines.so
>> (gdb) bt
>> #0  0x411c1960 in ATL_cdotc_xp0yp0aXbX () from 
>> /usr/lib/python2.3/site-packages/symeig/froutines.so
>> #1  0x411b5463 in cdotc_ () from 
>> /usr/lib/python2.3/site-packages/symeig/froutines.so
>> #2  0x41aac5fc in ?? () from
>
>
> <snip>
>
>> Any idea what is erroneous here ?
>>
>> Can someone reproduce the segmentation fault ?
>
>
> I cannot. Try building symeig against ATLAS 3.6.0 or Fortran LAPACK
> to see if the problem persists.
>
> Pearu
>
Now, I have used ATLAS3.6 but again I received a segmentation fault.

[GCC 3.3.3 (SuSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(no debugging symbols found)...(no debugging symbols found)...(no 
debugging symbols found)...>>> import symeig
(no debugging symbols found)...>>> symeig.test.test()
Random Seed:  (1268049219, 2102953867)
testComplex (symeig.test.test_symeig.SymeigTestCase) ...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1077041376 (LWP 20794)]
0x411c1960 in ATL_cdotc_xp0yp0aXbX () from 
/usr/lib/python2.3/site-packages/symeig/froutines.so
(gdb)

Any idea or suggestion how to  proceed ?

Nils

> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev at scipy.net
> http://www.scipy.net/mailman/listinfo/scipy-dev