[Numpy-discussion] Current SVN segfaults under VC7
zpincus at stanford.edu
Wed Mar 22 16:45:00 CST 2006
I've seen this too, and been able to fix it by removing the build
directory and rebuilding everything.
I wonder if there's a bug in numpy's dependency checking that's
causing certain files to not get rebuilt when they ought. I recently
updated to the SVN head, and numpy segfaulted on import, just as you
describe. After puttering around with GDB, it looked like some of the
code was out of synch with other parts of the code, so I decided to
rebuild from scratch.
After I deleted the entire numpy build directory ('python setup.py
clean' *did not* work) and re-built, things worked just fine. I've
also had this problem with scipy, and the same solution applied.
Anyhow, try removing all traces of build products from the numpy
directory and rebuilding... maybe that will fix things.
On Mar 22, 2006, at 4:30 PM, Tim Hochberg wrote:
> I just updated from CVS and compiled using VC7. The resulting numpy
> segfaults immediately on import. Do not pass go, do not collect
> $200. It's been a couple of weeks probably since I updated from
> CVS, so I'm not sure where to start looking. I suppose I could
> start going back in time until it works again and then see what
> checkins broke it, but if anyone has any better ideas, let me know.
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> that extends applications into web and mobile media. Attend the
> live webcast
> and join the prime developer group breaking into this new coding
> Numpy-discussion mailing list
> Numpy-discussion at lists.sourceforge.net
More information about the Numpy-discussion