I will be sure to use "gdb" and "bt" to get that information next time I
encounter the segmentation fault or any other error that I post to
list.  

I tried going back to the numpy.dev8106 version just now in an attempt
to recreate the conditions of the error, but I was unsuccessful in
generating any segmentation faults.  My guess is that I made some novice
mistake when upgrading the libraries from source.  

On Mon, 2010-02-22 at 10:16 -0500, Michael Droettboom wrote:
> Can you provide a gdb backtrace?
> 
> Run "gdb python", then at the gdb prompt type "run -c 'import pylab; 
> pylab.clf(); pylab.plot(pylab.sin(range(101))); pylab.xlabel("Test X"); 
> pylab.ylabel("Test Y"); pylab.show()'".  After it segfaults, type "bt" 
> to get a backtrace, and copy-and-paste it to this list.
> 
> Mike
> 
> Joseph D Cali wrote:
> > I am encountering the following error:
> >
> > python -c 'import pylab; pylab.clf(); pylab.plot(pylab.sin(range(101)));
> > pylab.xlabel("Test X"); pylab.ylabel("Test Y"); pylab.show()'
> >
> > /local_home/calijos/usr/lib/python2.6/site-packages/matplotlib/backends/backend_gtk.py:621:
> >  DeprecationWarning: Use the new widget gtk.Tooltip
> >   self.tooltips = gtk.Tooltips()
> > Segmentation fault
> >
> > -------------------------------------------------------------
> >
> > But when I run the following command, I encounter no errors and plot is
> > as expected:
> >
> > python -c 'import pylab; pylab.clf(); pylab.plot(pylab.sin(range(100)));
> > pylab.xlabel("Test X"); pylab.ylabel("Test Y"); pylab.show()'
> >
> > I tried several other plots, any plots with less than 100 points work
> > correctly, any plots with more than 100 points segfault.
> >
> > -------------------------------------------------------------
> >
> > My current system setup is:
> >
> > System: Ubuntu 9.04 x64
> > Python: Python 2.6.2
> > Matplotlib: >0.99.1 (tied 0.99.1.1, 0.99.1.2, and latest SVN version:
> > 8126)
> > Numpy Version: 1.5.0.dev8106
> >
> > I have been a long time Matplotlib user, and have never encountered this
> > issue.  It started whenever I updated numpy and scipy.  However,
> > reverting to the old version does not seem to fix the situation.  I also
> > cannot get numpy to crash on its own.  All my software works when
> > plotting is disabled.
> >
> > Has anyone else experienced this or similar problems during an upgrade?
> >
> > Joe
> >
> >
> >
> > ------------------------------------------------------------------------------
> > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> > http://p.sf.net/sfu/solaris-dev2dev
> > _______________________________________________
> > Matplotlib-users mailing list
> > Matplotlib-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >   
> 
-- 
Sincerely,
Joe


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Reply via email to