[SciPy-dev] symeig.test.test() segmentation fault

Nils Wagner nwagner at mecha.uni-stuttgart.de
Thu Nov 18 04:16:37 CST 2004


Hi all,
 
Afaik, Pearu is going to import symeig in scipy.
Therefore I would like to post to this mailing list

Finally I have used gdb python2.3 to trace back the segfault


GNU gdb 6.1
Copyright 2004 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/python2.3
(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 1077041376 (LWP 19966)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...Python 2.3.3 (#1, Apr  6 2004, 01:47:39)
[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 19966)]
0x411c1960 in ATL_cdotc_xp0yp0aXbX () from /usr/lib/python2.3/site-packages/symeig/froutines.so
(gdb)

Any suggestion, how to fix the segmentation fault ?

Nils





More information about the Scipy-dev mailing list