[Numpy-discussion] Re: floating point exception weirdness (Andrew Straw)

Andrew Straw strawman at astraw.com
Mon Nov 1 22:12:15 CST 2004

I filed a bug report on this with the Debian bug tracking system. (See 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=279294 ) It looks like 
it's fixed in the upstream glibc sources -- the Debian maintainers just 
have to apply the patch, so hopefully it won't take too long.


On Nov 1, 2004, at 3:32 PM, Andrew Straw wrote:

> Steve Chaplin wrote:
>>> Just a small addendum, (which I hope will spur on bug-fixing once 
>>> Todd et al. are back from the conference -- let me know if I should 
>>> file a sourceforge bug report):
>> I've not read all this thread so I don't know the full background. 
>> But I
>> had a floating point / SSE problem using numarray.
>> It turned out to be a glibc not numarray problem and was solved by
>> upgrading glibc.
>> http://sources.redhat.com/bugzilla/show_bug.cgi?id=10
>> There was also a SourceForge bug report but I can't locate it.
> The test code you filed with the RedHat bugzilla report at the URL you 
> gave (above) does indeed produce the bug you mention in that bug 
> report.  So, I now think this is not a numarray bug, but a debian/libc 
> bug.
> Thanks for your help, Steve -- I never would have found this myself.
> Now thinking about how to fix my glibc...
> Andrew
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/numpy-discussion

More information about the Numpy-discussion mailing list