scipy.test troubles (was Re: [SciPy-dev] Stupid question.)
Prabhu Ramachandran
prabhu at aero.iitm.ernet.in
Wed Feb 20 14:17:45 EST 2002
>>>>> "eric" == eric <eric at scipy.org> writes:
>> I guess it serves me right to keep updating from CVS and
>> trying. :(
eric> This was added when the test suites were upgraded. The CVS
eric> version has the corrct files there. I'm not sure why update
eric> didn't synchronize your sandbox correctly.
Yes, a clean install works fine. Atleast it imports fine and some of
my code runs fine. However the tests fail after a point. I get a
segmentation fault. Here is the relavant segment:
(gdb) r
Starting program: /usr/local/bin/python
[New Thread 1024 (LWP 8670)]
Python 2.1.1 (#1, Nov 12 2001, 19:01:44)
[GCC 2.95.4 20011006 (Debian prerelease)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import scipy
>>> scipy.test()
[...]
No test suite found for scipy.integrate
......................E.......E......E....................................................................................
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 8670)]
0x40e03ed6 in array_from_pyobj (type_num=7, dims=0xbfffe93c, rank=2, intent=2,
obj=0x84992c0)
at /usr/local/lib/python2.1/site-packages/f2py2e/src/fortranobject.c:492
492 if (PyArray_Check(obj)) { /* here we have always intent(in) or
(gdb) back
#0 0x40e03ed6 in array_from_pyobj (type_num=7, dims=0xbfffe93c, rank=2,
intent=2, obj=0x84992c0)
at /usr/local/lib/python2.1/site-packages/f2py2e/src/fortranobject.c:492
#1 0x40e0c8f2 in f2py_rout_flapack_dgeev (capi_self=0x8293290,
capi_args=0x85c89d4, capi_keywds=0x85da5c4, f2py_func=0x405bf260 <dgeev_>)
at build/temp.linux-i686-2.1/flapackmodule.c:5631
#2 0x40e038cd in fortran_call (fp=0x8293290, arg=0x85c89d4, kw=0x85da5c4)
at /usr/local/lib/python2.1/site-packages/f2py2e/src/fortranobject.c:243
#3 0x08059f9d in call_object (func=0x8293290, arg=0x85c89d4, kw=0x85da5c4)
at Python/ceval.c:2813
[...]
Well, maybe I have to update my f2py install as well. I might have a
broken version (I updated the cvs copy a few days back).
Is this a good time to update my f2py also?
thanks,
prabhu
More information about the SciPy-Dev
mailing list