Le vendredi 14 mai 2010 à 10:06 -0400, Michael Droettboom a écrit :
> Can you get a gdb backtrace?
>
> (Run "gdb python", then "run name_of_script.py", cause it to crash, and
> type "bt" in gdb console...)
Here is the backtrace:
(gdb) run test_plt.py
Starting program: /usr/bin/python test_plt.py
[Thread debugging using libthread_db enabled]
/usr/lib/pymodules/python2.5/matplotlib/backends/backend_gtk.py:621:
DeprecationWarning: Use the new widget gtk.Tooltip
self.tooltips = gtk.Tooltips()
Program received signal SIGILL, Illegal instruction.
0xb767b638 in ATL_diamax_xp1yp0aXbX ()
from /usr/lib/libblas.so.3gf
(gdb) bt
#0 0xb767b638 in ATL_diamax_xp1yp0aXbX ()
from /usr/lib/libblas.so.3gf
#1 0x00000000 in ?? ()
(gdb)
Surprisingly, the troubles come from libblas. In fact, I daily update my
debian and, on wednesday, the package libatlas3gf-base has been updated
from 3.8.3-21 to 3.8.3-22. It seems that it had some side-effect on
matplotlib behaviour...
But why does the interpreter crash only when the pointer enters the
figure canvas??
--
Fabrice Silva <si...@lma.cnrs-mrs.fr>
LMA UPR CNRS 7051
------------------------------------------------------------------------------
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
