rex rex at nosyntax.com writes:
There doesn't appear to be a problem with recent versions of the
software. In particular, ATLAS 3.7.33 does not cause an error.
Is there some reason for you to use such old software? (gcc 3.3.1
kernel 2.4.21)? What platform are you building for?
-rex
john,
there was a bug that made it into debian sarge whereby a SIGFPE wasn't
trapped in the appropriate place and ended up causing problems similar
to what you describe. the difficulty in debugging is that you're after
whatever triggers the FPE in the first place (or the bug that lets it go
On 6/23/07, rex [EMAIL PROTECTED] wrote:
Stefan van der Walt [EMAIL PROTECTED] [2007-06-23 15:06]:
On Sat, Jun 23, 2007 at 07:35:35PM +, John Ollinger wrote:
I have just been updating our version of Python, numpy and scipy and
have run
into a floating point exception that crashes
Charles R Harris [EMAIL PROTECTED] [2007-06-24 06:22]:
On 6/23/07, rex [EMAIL PROTECTED] wrote:
Stefan van der Walt [EMAIL PROTECTED] [2007-06-23 15:06]:
On Sat, Jun 23, 2007 at 07:35:35PM +, John Ollinger wrote:
I have just been updating our version of Python, numpy and
scipy
At 11:09 AM 6/24/2007, you wrote:
On 6/24/07, rex
[EMAIL PROTECTED]
wrote:
Charles R Harris
[EMAIL PROTECTED] [2007-06-24 06:22]:
On 6/23/07, rex
[EMAIL PROTECTED] wrote:
Stefan van der Walt
[EMAIL PROTECTED]
[2007-06-23 15:06]:
On Sat, Jun 23, 2007 at 07:35:35PM +, John
John Ollinger [EMAIL PROTECTED] [2007-06-24 13:13]:
I am running gcc 3.3.1 on SuSe Linux 2.4.21-144-smp4G. The error
first occurred with numpy-1.0.3. I downloaded svn 3875 when I
then
read the scipy web page and installed the latest subversion. The
test
I have just been updating our version of Python, numpy and scipy and have run
into a floating point exception that crashes Python when I test the release.
I am running gcc 3.3.1 on SuSe Linux 2.4.21-144-smp4G. The error first occurred
with numpy-1.0.3. I downloaded svn 3875 when I then read
Stefan van der Walt [EMAIL PROTECTED] [2007-06-23 15:06]:
On Sat, Jun 23, 2007 at 07:35:35PM +, John Ollinger wrote:
I have just been updating our version of Python, numpy and scipy and have
run
into a floating point exception that crashes Python when I test the
release.
