Hi,
>> I've been having an almost identical problem with described above with
>> the MacOSX backend. When I switched to the TkAgg backend, the segfault
>> occurs when I try pylab.close() instead.
>>
> I may have had the same problem. Do you happen to be on a recent revision?
>
> Christoph Gohlke
On Nov 30, 2009, at 9:09 AM, Jcmottram wrote:
>
> Hi,
> I've been having an almost identical problem with described above with
> the MacOSX backend. When I switched to the TkAgg backend, the segfault
> occurs when I try pylab.close() instead.
>
>
I may have had the same problem. Do you happ
Hi,
I've been having an almost identical problem with described above with
the MacOSX backend. When I switched to the TkAgg backend, the segfault
occurs when I try pylab.close() instead.
Do you get the segmentation fault also with other backends (e.g. Tkagg) or
only with the MacOSX backend?
Do you get the segmentation fault also with other backends (e.g. Tkagg) or only
with the MacOSX backend?
--Michiel.
--- On Sun, 11/29/09, Matthew Brett wrote:
> From: Matthew Brett
> Subject: Re: [matplotlib-devel] Segmentation fault from fresh OSX snow
> leopard build
> To
On Sun, Nov 29, 2009 at 9:49 AM, Jouni K. Seppänen wrote:
> Matthew Brett
> writes:
>
>>> Can you get a backtrace in gdb?
>>
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> Reason: 13 at address: 0x
>> 0x000102d96ffb in py_to_agg_transformation_matrix
>>
Matthew Brett
writes:
>> Can you get a backtrace in gdb?
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: 13 at address: 0x
> 0x000102d96ffb in py_to_agg_transformation_matrix
> (obj=0x102d794d0, errors=false) at src/agg_py_transforms.cpp:21
> 21
Hi,
>> Can you get a backtrace in gdb?
>
> (gdb) run scipybuild/matplotlib/examples/pylab_examples/simple_plot.py
...
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: 13 at address: 0x
> 0x000102d96ffb in py_to_agg_transformation_matrix
> (obj=0x102d
Hi,
On Sun, Nov 29, 2009 at 1:30 AM, Jouni K. Seppänen wrote:
> Matthew Brett writes:
>
>> I am rashly building matplotlib from source on Snow Leopard, and
>> getting a segmentation fault as soon as I try and do a plot.
>
> Can you get a backtrace in gdb?
(gdb) run scipybuild/matplotlib/example
Matthew Brett writes:
> I am rashly building matplotlib from source on Snow Leopard, and
> getting a segmentation fault as soon as I try and do a plot.
Can you get a backtrace in gdb?
--
Jouni K. Seppänen
http://www.iki.fi/jks
> I am rashly building matplotlib from source on Snow Leopard, and
> getting a segmentation fault as soon as I try and do a plot.
>
> me $ python -c 'import pylab; pylab.plot(range(10))'
> Segmentation fault
Sorry - here the is top of the build output:
export PKG_CONFIG_PATH="/Users/mb312/usr/loc
Hi,
I am rashly building matplotlib from source on Snow Leopard, and
getting a segmentation fault as soon as I try and do a plot.
me $ python -c 'import pylab; pylab.plot(range(10))'
Segmentation fault
I've built python myself with:
export MACOSX_DEPLOYMENT_TARGET=10.6
./configure --prefix=/Use
11 matches
Mail list logo
