, to print out argv[4]
from the debugger.
Thanks for helping with this. Hopefully we're honing in on something.
Mike
Malte Marquarding wrote:
Hi,
The segv also occurs in matplotlib-0.90.1. A clean build doesn't
help.
Here is the gdb output, looks like something is pointing
to stringstream, we are c++
er's anyway.
I will check out the svn and send a patch. Where do I send it to?
Cheers,
Malte
On 15/05/2008, at 8:40 AM, Malte Marquarding wrote:
Hi,
unfortunately 32-bit ;-) I tried digging around, but I don't know
much about tcl/tk. Seeing a char string argv atol'ed
Hi
Attached is the the patch. It uses stringstream, so I don't know if
it will work on all platforms. I am not a windows person ;-)
I didn't read your email properly about the existence of atoll, so
as I am a c++er I am a bit more comfortable with stringstream.
Cheers,
Malte.
Hi,
The segv also occurs in matplotlib-0.90.1. A clean build doesn't help.
Here is the gdb output, looks like something is pointing into nirvana..
(gdb) p bboxo
$1 = value optimized out
(gdb) p bbox
$2 = (Bbox *) 0x7ffb
(gdb) p bbox-_ll
Cannot access memory at address 0x7ffb
Cheers,
Hi,
I had a look through the archives but couldn't find an answer to this.
Using the tkagg backend (agg is fine) I get a segmentation fault
doing a simple plot.
gdb returns the following:
362 Point* ll_api() {return _ll;}
Current language: auto; currently c++
(gdb) bt
#0 0xb6fc1bac in
Hi,
Not that it helps you, but I have a created python2.4 egg.
matplotlib-0.91.2-py2.4-macosx-10.4-fat.egg
It is build against numpy-1.0.4 and with the TkAgg backend.
Is there some way of contributing it to the larger community.
Cheers,
Malte
Christopher Barker wrote:
Hi all,
I notice
