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
On Thu, Jul 8, 2010 at 11:13 AM, Tony S Yu tsy...@gmail.com 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
Can you get a gdb backtrace?
Mike
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
On Jul 8, 2010, at 12:27 PM, Michael Droettboom wrote:
Can you get a gdb backtrace?
Mike
This is as far as I can get with gdb:
#-
$ gdb python
GNU gdb 6.3.50-20050815 (Apple version gdb-1461.2) (Fri Mar 5 04:43:10 UTC
2010)
Copyright 2004 Free Software Foundation, Inc.
GDB is
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] ***
On 07/08/2010 02:38 PM, John Hunter wrote:
On Thu, Jul 8, 2010 at 1:25 PM, Tony S Yutsy...@gmail.com wrote:
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
On Jul 8, 2010, at 2:51 PM, Michael Droettboom wrote:
On 07/08/2010 02:38 PM, John Hunter wrote:
On Thu, Jul 8, 2010 at 1:25 PM, Tony S Yutsy...@gmail.com wrote:
On Jul 8, 2010, at 12:27 PM, Michael Droettboom wrote:
Can you get a gdb backtrace?
Mike
Ignore my last email. The
