On Mon, Aug 3, 2009 at 6:32 PM, Steven Coutts<ste...@couttsnet.com> wrote: > David Cournapeau wrote: > >> >> Do you mean that if you build with debug information, everything else >> being equal, you cannot reproduce the crashes ? >> >> cheers, >> >> David > > That does appear to be the case, SciPy 1.7.0 is now also running fine.
It is just getting weirder - the fact that numpy worked with bare BLAS/LAPACK and crashed with atlas lead me to think that it was an atlas problem. But now, this smells more like a compiler problem. I would first really check that the only difference between crash vs. no crash is debug vs non debug (both with ATLAS), to avoid chasing wrong hints. Practically, I would advised you to "clone" the numpy sources (one debug, one non debug), and build from scratch with a script to do things in a repeatable manner. Then, if indeed you have crash only with non debug build, I would recommend to install my project numscons, to be able to "play" with flags, and first try building with the exact same flags as a normal build, but adding the -g flag. For example: CFLAGS="-O2 -fno-strict-aliasing -g" python setupscons.py install --prefix=blabla Hopefully, you will be able to reproduce the crash and get a backtrace, cheers, David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion