[NumPy-Tickets] [NumPy] #1737: numpy.test() seg faults
NumPy Trac
numpy-tickets@scipy....
Tue Feb 8 15:47:17 CST 2011
#1737: numpy.test() seg faults
------------------------+---------------------------------------------------
Reporter: sienkiew | Owner: somebody
Type: defect | Status: new
Priority: high | Milestone: 2.0.0
Component: numpy.core | Version: devel
Keywords: |
------------------------+---------------------------------------------------
Comment(by m-paradox):
Hmmm, it's hard to see what could be causing this crash, since the
function it's crashing in is pretty straightforward. I've just committed a
fix to one bug in the function, which I doubt was causing the crash but I
could be wrong. There are two things you could do to help narrow down the
cause further:
- Get the gdb backtrace to include NumPy line numbers. It has the
symbols, but this would narrow things down better. I suspect this
requires compiling NumPy with some more debug options, but I'm not sure
exactly what is needed.
- Enable the printf tracing built into
numpy/core/src/umath/ufunc_object.c. Near the top, there is a section
like this:
{{{
/********** PRINTF DEBUG TRACING **************/
#define NPY_UF_DBG_TRACING 0
#if NPY_UF_DBG_TRACING
#define NPY_UF_DBG_PRINTF(...) printf(__VA_ARGS__)
#else
#define NPY_UF_DBG_PRINTF(...)
#endif
/**********************************************/
}}}
If you change the 0 to a 1, it will print out a lot of information about
the ufunc evaluation while it's running, and this may provide some clues
as to what's going wrong.
--
Ticket URL: <http://projects.scipy.org/numpy/ticket/1737#comment:2>
NumPy <http://projects.scipy.org/numpy>
My example project
More information about the NumPy-Tickets
mailing list