On Jul 8, 2010, at 12:27 PM, Michael Droettboom wrote:

> Can you get a gdb backtrace?
> 
> Mike

Ignore my last email. The crash occurs here:

#---
Continuing.
Reading symbols for shared libraries . done
Reading symbols for shared libraries + done
2010-07-08 14:15:20.218 Python[60899:d13] *** __NSAutoreleaseNoPool(): Object 
0x1048a86d0 of class NSCFNumber autoreleased with no pool in place - just 
leaking
Reading symbols for shared libraries + done
Reading symbols for shared libraries + done
Reading symbols for shared libraries ++ done
Reading symbols for shared libraries + done
Reading symbols for shared libraries + done
Reading symbols for shared libraries + done
Reading symbols for shared libraries + done
Reading symbols for shared libraries + done
Reading symbols for shared libraries + done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000003000000040
agg::pod_bvector<agg::point_base<double>, 6u>::~pod_bvector 
(this=0x7fff5fbf8130) at agg_array.h:521
521                     pod_allocator<T>::deallocate(*blk, block_size);
#---

and the first few lines of the traceback are here:

#---
#0  agg::pod_bvector<agg::point_base<double>, 6u>::~pod_bvector 
(this=0x7fff5fbf8130) at agg_array.h:521
#1  0x0000000101795b65 in ~vertex_sequence [inlined] () at 
/Users/Tony/python/devel/mpl/agg24/include/agg_vertex_sequence.h:525
#2  0x0000000101795b65 in agg::vcgen_stroke::~vcgen_stroke 
(this=0x7fff5fbf80c8) at agg_vcgen_stroke.h:32
#3  0x000000011a45ea07 in ~rasterizer_cells_aa [inlined] () at 
kiva_graphics_context.h:410
#4  0x000000011a45ea07 in ~rasterizer_scanline_aa [inlined] () at 
/Users/Tony/python/devel/enthought/Enable/enthought/kiva/agg/agg-24/include/agg_rasterizer_cells_aa.h:101
#---

I posted the full traceback on pastebin: http://pastebin.com/ViefksDC

Are there conflicting versions of agg?

-Tony



> 
> On 07/08/2010 12:13 PM, Tony S Yu wrote:
>> The recent "nasty import behavior" thread motivated me to post an issue I've 
>> been having with matplotlib and chaco. (I've posted to the Chaco list 
>> previously, without much luck.)
>> 
>> If I import matplotlib and chaco at the same time, I get a segmentation 
>> fault in the _path.so plugin.  Below is a simple script that segfaults on my 
>> computer.
>> 
>> I should note that this is installation dependent; someone on the Chaco list 
>> only had the issue with certain versions of Python. Just for reference, I'm 
>> on OS X 10.6, Python 2.6.1, and matplotlib/chaco trunk.
>> 
>> -Tony

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to