On Wed, Jan 12, 2011 at 10:23 AM, Hannes Kutza <ku...@pik-potsdam.de> wrote:

> i think now it's mainly the savefig() that provokes that malloc error…
>
> Anfang der weitergeleiteten E-Mail:
>
> *Von: *Hannes Kutza <ku...@pik-potsdam.de>
> *Datum: *12. Januar 2011 14:35:24 MEZ
> *An: *matplotlib-us...@lists.sourceforge.net
> *Betreff: **malloc error on show() oder x/ylabel()*
>
> i'm running python 2.7, matplotlib-1.0.1, gcc 4.2.1 and grortran 4.2.1…
> when invoking (successful importing *import matplotlib.pyplot as plt*)
> plt.show() in combination with plt.xlabel or savefig("fig.ps") give me
> that nasty malloc error:
>
> Python(19725,0x7fff7055fca0) malloc: *** error for object 0x102d8c6c0:
> pointer being freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
> Abort trap
>
> calling plt.show or x/ylabel("string..") alone doesn't get me that error…
>
> cheers,
> hannesk
>
>
>
Hannesk,

Most likely the issue here is a bad or mixed build.  Assuming that you built
the current install of matplotlib 1.0.1 from source, how did you have your
previous install (packaged or from source)?  Did you completely remove that
install before building the current install?

Ben Root
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Reply via email to