[Numpy-discussion] Scalar math module is ready for testing

Ed Schofield schofield at ftw.at
Fri Apr 28 01:32:00 CDT 2006


Travis Oliphant wrote:
>
> The scalar math module is complete and ready to be tested.  It should
> speed up code that relies heavily on scalar arithmetic by by-passing
> the ufunc machinery.

Excellent!

> It needs lots of testing to be sure that it is doing the "right" thing.

With revision 2454 I get a segfault in numpy.test() after importing
numpy.core.scalarmath:

check_1 (numpy.distutils.tests.test_misc_util.test_appendpath) ... ok
check_2 (numpy.distutils.tests.test_misc_util.test_appendpath) ... ok
check_3 (numpy.distutils.tests.test_misc_util.test_appendpath) ... ok
check_gpaths (numpy.distutils.tests.test_misc_util.test_gpaths) ... ok
check_1 (numpy.distutils.tests.test_misc_util.test_minrelpath) ... ok
check_singleton (numpy.lib.tests.test_getlimits.test_double)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208403744 (LWP 11232)]
0xb7142cf7 in int_richcompare (self=0x81c0ab8, other=0x8141dbc, cmp_op=3)
    at build/src.linux-i686-2.4/numpy/core/src/scalarmathmodule.c:19120
19120           PyArrayScalar_RETURN_TRUE;
(gdb) bt
#0  0xb7142cf7 in int_richcompare (self=0x81c0ab8, other=0x8141dbc,
cmp_op=3)
    at build/src.linux-i686-2.4/numpy/core/src/scalarmathmodule.c:19120
#1  0x0807ce1f in PyObject_Print ()
#2  0x0807e451 in PyObject_RichCompare ()

Is this helpful?

-- Ed





More information about the Numpy-discussion mailing list