[SciPy-dev] scipy 0.6.0 tests kill python interpreter
Ondrej Certik
ondrej@certik...
Sat Dec 1 17:00:11 CST 2007
On Dec 1, 2007 11:06 PM, Robert Kern <robert.kern@gmail.com> wrote:
> Ondrej Certik wrote:
> > On Dec 1, 2007 10:44 PM, Robert Kern <robert.kern@gmail.com> wrote:
> >> Ondrej Certik wrote:
> >>> Hi,
> >>>
> >>> if I install scipy 0.6.0 on Debian and run tests, it kills the
> >>> interpreter with Illegal instruction.
> >>>
> >>> More details here:
> >>>
> >>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452991
> >>>
> >>> Is anyone able to reproduce it on their system, or is it just related
> >>> to Debian? Could you please send me
> >>> the correct run of tests, so that I can discover where exactly it differs?
> >> Try scipy.test(verbosity=1). This will print the name of the test before it runs
> >> the test. Also, try running Python under gdb so we can get a backtrace.
> >
> > It doesn't seem to help much:
> >
> >>>> import scipy
> > s>>> scipy.test(verbosity=1)
>
> My apologies.
>
> scipy.test(verbosity=2)
boundary modes/usr/lib/python2.4/site-packages/scipy/ndimage/interpolation.py:41:
UserWarning: Mode "reflect" may yield incorrect results on boundaries.
Please use "mirror" instead.
warnings.warn('Mode "reflect" may yield incorrect results on '
... ok
center of mass 1 ... ok
center of mass 2 ... ok
center of mass 3 ... ok
center of mass 4 ... ok
center of mass 5 ... ok
center of mass 6 ... ok
center of mass 7 ... ok
center of mass 8 ... ok
center of mass 9 ... ok
correlation 1 ... ok
correlation 2 ... ok
correlation 3 ... ok
correlation 4 ... ok
correlation 5 ... ok
correlation 6 ... ok
correlation 7 ... ok
correlation 8 ... ok
correlation 9 ... ok
correlation 10 ... ok
correlation 11 ... ok
correlation 12 ... ok
correlation 13 ... ok
correlation 14 ... ok
correlation 15 ... ok
correlation 16 ... ok
correlation 17 ... ok
correlation 18 ... ok
correlation 19 ... ok
correlation 20 ... ok
correlation 21 ... ok
correlation 22 ... ok
correlation 23 ... ok
correlation 24 ... ok
correlation 25 ... ok
brute force distance transform 1 ... ok
brute force distance transform 2 ... ok
brute force distance transform 3 ... ok
brute force distance transform 4 ... ok
brute force distance transform 5 ... ok
brute force distance transform 6 ... ok
chamfer type distance transform 1 ... ok
chamfer type distance transform 2 ... ok
chamfer type distance transform 3 ... ok
euclidean distance transform 1 ... ok
euclidean distance transform 2 ... ok
euclidean distance transform 3 ... ok
euclidean distance transform 4 ... ok
line extension 1 ... ok
line extension 2 ... ok
line extension 3 ... ok
line extension 4 ... ok
line extension 5 ... ok
line extension 6 ... ok
line extension 7 ... ok
line extension 8 ... ok
line extension 9 ... ok
line extension 10 ... ok
extrema 1 ... ok
extrema 2 ... ok
extrema 3 ... ok
extrema 4 ... ok
find_objects 1 ... ok
find_objects 2 ... ok
find_objects 3 ... ok
find_objects 4 ... ok
find_objects 5 ... ok
find_objects 6 ... ok
find_objects 7 ... ok
find_objects 8 ... ok
find_objects 9 ... ok
ellipsoid fourier filter for complex transforms 1 ... ok
ellipsoid fourier filter for real transforms 1 ... ok
gaussian fourier filter for complex transforms 1 ... ok
gaussian fourier filter for real transforms 1 ... ok
shift filter for complex transforms 1 ... ok
shift filter for real transforms 1 ... ok
uniform fourier filter for complex transforms 1 ... ok
uniform fourier filter for real transforms 1 ... ok
gaussian filter 1 ... ok
gaussian filter 2 ... ok
gaussian filter 3 ... ok
gaussian filter 4 ... ok
gaussian filter 5 ... ok
gaussian filter 6 ... ok
gaussian gradient magnitude filter 1 ... ok
gaussian gradient magnitude filter 2 ... ok
gaussian laplace filter 1 ... ok
gaussian laplace filter 2 ... ok
generation of a binary structure 1 ... ok
generation of a binary structure 2 ... ok
generation of a binary structure 3 ... ok
generation of a binary structure 4 ... ok
generic filter 1Illegal instruction
>
> > But when running through gdb, it says:
> >
> > warnings.warn('Mode "reflect" may yield incorrect results on '
> > .............................................................................................
> > Program received signal SIGILL, Illegal instruction.
> > [Switching to Thread 0xb7e278c0 (LWP 28932)]
> > 0xb6b83d43 in ?? ()
> > from /usr/lib/python2.4/site-packages/scipy/ndimage/_nd_image.so
> > (gdb) bt
> > #0 0xb6b83d43 in ?? ()
> > from /usr/lib/python2.4/site-packages/scipy/ndimage/_nd_image.so
> > #1 0xbf99bdd8 in ?? ()
> > #2 0xb6b87211 in NI_GenericFilter ()
> > from /usr/lib/python2.4/site-packages/scipy/ndimage/_nd_image.so
> > Backtrace stopped: frame did not save the PC
> > (gdb)
> >
> >
> > I don't have time to dig into this and fix it myself, but if you tell
> > me what else to try, I will.
>
> Building scipy with debug symbols might help make the gdb backtrace more
> helpful, but let's wait for the results of verbosity=2.
>
> python setup.py build_ext -g build
Maybe you already know where the problem is. If not, I'll try to build
scipy with debug symbols and try it again.
Ondrej
More information about the Scipy-dev
mailing list