[Numpy-discussion] Fwd: SSE2 segfault
Fri Dec 21 02:11:42 CST 2007
forwarding more information about the problem + backtrace.
---------- Forwarded message ----------
From: Jan Medlock <email@example.com>
Date: Dec 21, 2007 4:17 AM
Subject: Re: Bug#448530: bug reproduced
To: Ondrej Certik <firstname.lastname@example.org>
Cc: email@example.com, Kumar Appaiah <firstname.lastname@example.org>
On Thu, Dec 20, 2007 at 08:01:01PM +0100, Ondrej Certik wrote:
> Paul Metcalfe has sent me this explanation:
> I think it's a packaging problem with linear algebra.
I'm still here. I saw the bug in the NumPy bug tracker that
suggests the problem is specific to Debian & Ubuntu and Paul
Metcalfe's details about linking.
Linking against ATLAS instead of BLAS & LAPACK may indeed ultimately
be the problem and I'm afraid I don't understand the details. That
said, I believe the problem is SSE2 specific. The machine that I'm
having the problem with is an Intel Pentium4 with SSE2, but I also
have an AMD K7 machine that has 3DNow but not SSE2. The AMD machine
does not exhibit the bug with the 3DNow version of ATLAS. (Of course
neither do with the SSE or base versions of ATLAS.)
I haven't participated in the thread on the NumPy mailing list because
I don't see a way to reply to the thread since I wasn't subscribed at
Attached is a gdb backtrace. Please let me know how I can make it
more informative, if necessary.
Thanks again for tracking down this bug,
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the Numpy-discussion