[SciPy-dev] missing Lib/__init__.py in newscipy?

Travis Oliphant oliphant at ee.byu.edu
Wed Oct 19 12:46:35 CDT 2005


Arnd Baecker wrote:

>On Wed, 19 Oct 2005, Pearu Peterson wrote:
>
>  
>
>>On Wed, 19 Oct 2005, Robert Cimrman wrote:
>>
>>    
>>
>>>In [1]:import scipy
>>>Importing io to scipy
>>>Importing special to scipy
>>>Segmentation fault (SIGSEGV)
>>>      
>>>
>>This issue is now fixed in SVN (segfaults occured probably due to a bug in
>>_cephesmodule.c). special now imports succesfully on my debian x86_64 box.
>>
>>However, there are probably more places where we need to make int->intp
>>changes for 64-bit platforms.
>>    
>>
>
>I fear so - the
>In [1]: from scipy.linalg import fblas
>Importing io to scipy
>Importing special to scipy
>Importing utils to scipy
>Importing interpolate to scipy
>Importing optimize to scipy
>Importing linalg to scipy
>
>In [2]: fblas.sger(1,[1,2],[3,4])
>Segmentation fault
>  
>
The first thing to do is to look for warnings in the compilation of 
fblasmodule.c that might  lead to int->intp problems.

I did not see anything significant in the build log you last sent, but I 
might have missed something.

The next thing to do is to track down where the segfault is happening.   
You could try running gdb

gdb
file <path>/<to>/<your>/<python>
run
from scipy.linalg import fblas
fblas.sger(1,[1,2],[3,4])

gdb will catch the segfault and show you where it died. 

As a last resort, I insert print statements to guide me where the code 
is dying and carefully inspect that section of code.

-Travis







More information about the Scipy-dev mailing list