matplotlib-devel Mailing List for matplotlib

Hello everybody,
On Wed, Dec 01, 2004 at 06:38:47PM -0800, Andrew Straw wrote:
> It sounds like you may have hit a nasty glibc bug that caused me much=20
> head scratching over the months. Check this thread:
>=20
> http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/2207861
>=20
> Bottom line:
>=20
> numarray does The Right Thing and attempts to set up floating point=20
> exception handling, but older versions of glibc (such as that in Debian=
=20
> sarge) have a bug whereby the floating point error bits in the SSE are=20
> not properly cleared, leading to a SIGFPE terminating the program the=20
> next time the SSE unit is used.
Yes, this was the problem. I applied the patch from
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D279294
and the problem disappeared. Does this imply that on current
Debian/unstable systems matplotlib can only be used with
python-numeric and not with python-numarray?
By the way: I am still interested in my original question. How would
I use a debugger etc. to find the problem myself in such a situation?
Many thanks,
Jochen
--=20
http://seehuhn.de/

On Sat, 2004年12月04日 at 19:10 +0100, Norbert Nemec wrote:
> Hi there,
> 
> can anybody reproduce these bugs:
> 
> * when I first use the interactive zoom&move feature and then switch over to 
> the zoom-to-box mode, the mode is not completely switched, but stays in some 
> broken intermediate state: using the mouse, I can draw a box, but at the same 
> time, the plot is moved along with the mouse (like in interactive mode)
I can't reproduce this problem.
> * when I zoom in *very* close, (probably near the limit of floating point 
> resolution), I suddenly see huge garbage polygons in the plot. Probably there 
> should be some check limiting the zoom to the range of floating point values?
I do get this one. It looks like an Agg backend bug because it happens
for me on TkAgg and GTKAgg, but not GTK or GTKCairo.
Steve