[Numpy-discussion] ANN: Numpy 1.6.0 release candidate 1
Charles R Harris
charlesr.harris at gmail.com
Sat Apr 30 21:37:34 EDT 2011
On Sat, Apr 30, 2011 at 6:50 PM, Christoph Gohlke <cgohlke at uci.edu> wrote:
> On 4/30/2011 4:58 PM, Charles R Harris wrote:
> > On Sat, Apr 30, 2011 at 5:53 PM, Charles R Harris
> > <charlesr.harris at gmail.com <mailto:charlesr.harris at gmail.com>> wrote:
> > <snip>
> > I get a null pointer access violation during numpy.test() with
> > msvc9/MKL builds for win32 (not win-amd64). The crash occurs
> > test_result_type() in test_numeric.py and can be reduced to the
> > following code:
> > > >> import numpy as np
> > > >> np.result_type(np.array([np.float32(0)]), np.complex128(0))
> > np.float64(0) and np.float16(0) also crash. Unfortunately the
> > builds do not crash.
> > This is new, right?
> > Does it depend on the optimization level?
> > Chuck
> Yes it's new. The pure msvc9 builds without MKL also crash. The crash
> disapperars When compiling with /Od (disable optimization) instead of
> /Ox (maximum optimization; the default for distutils).
So all of np.float16(0), np.float32(0), np.float64(0), etc crash? Does it
depend at all on 0 as the argument, or is it the same for 1, 0.0, etc. What
about string arguments like np.float64("0"). I want to pin the location down
a bit more. Too bad it doesn't crash in the debugger.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion