On 4/30/2011 6:37 PM, Charles R Harris wrote: > > > On Sat, Apr 30, 2011 at 6:50 PM, Christoph Gohlke <cgoh...@uci.edu > <mailto:cgoh...@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.har...@gmail.com <mailto:charlesr.har...@gmail.com> > <mailto:charlesr.har...@gmail.com > <mailto:charlesr.har...@gmail.com>>> wrote: > > > > <snip> > > > > > > I get a null pointer access violation during numpy.test() > with all > > msvc9/MKL builds for win32 (not win-amd64). The crash > occurs during > > 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 debug > > 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. > > Chuck >
Sorry, I should have been more precise. The crash occurs in `numpy.result_type(a, b)` with the following inputs: b = numpy.complex128(0) a = numpy.array([numpy.float16(0)]) a = numpy.array([numpy.float32(0)]) a = numpy.array([numpy.float64(0)]) Christoph _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
