[Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray
Wed Jul 18 19:24:12 CDT 2012
On Wed, Jul 18, 2012 at 7:25 PM, Ralf Gommers
> On Wed, Jul 18, 2012 at 1:24 PM, Ondřej Čertík <email@example.com>
>> I managed to compile NumPy in MinGW under Wine in Ubuntu 11.10 and
>> here is a full log of the tests:
>> It fails at the test test_str (test_arrayprint.TestComplexArray) with
>> a segfault like this:
>> test_str (test_arrayprint.TestComplexArray) ... wine: Unhandled page
>> fault on read access to 0x00000000 at address (nil) (thread 0009),
>> starting debugger...
>> Unhandled exception: page fault on read access to 0x00000000 in 32-bit
>> code (0x00000000).
>> Register dump:
>> CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
>> EIP:00000000 ESP:0041c230 EBP:00000000 EFLAGS:00010202( R- -- I - - -
>> EAX:00000000 EBX:1e00807f ECX:00000000 EDX:0041c208
>> ESI:00f46de0 EDI:00000000
>> See the gist for the full log. Any ideas? I downloaded Python from
>> python.org, is it supposed to work with numpy compiled using mingw?
> It is. I have Python 2.5 ... 3.2 from Python.org, with MinGW from
> http://prdownloads.sourceforge.net/mingw/MinGW-5.0.3.exe?download and ATLAS
> binaries from https://github.com/numpy/vendor.
> Then I normally build numpy/scipy with "paver bdist_wininst_simple" or
> "paver bdist_wininst_superpack". This also requires MakeNSIS and the CpuId
> plugin for it, as documented at
Thanks for the details. I'll try to reproduce it. I have no idea why
my setup doesn't work.
I've nailed it to:
>>> import numpy as np
>>> np.array([complex(0, 1)], np.complex64)
wine: Unhandled page fault on read access to 0x00000000 at address
(nil) (thread 0009), starting debugger...
So it is something with the complex types.
More information about the NumPy-Discussion