Re: [Matplotlib-users] tkinter segv under opensuse 10.3

qEric Firing wrote: > Michael Droettboom wrote: >> Yes, it looks like if it were an "unsigned int", we would have been >> okay. That looks like (essentially) what your patch does, but in a >> C++ idiom. I'll submit your patch and put a note out to the Windows >> guys to help test it. There's

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

Eric Firing wrote: > Michael Droettboom wrote: >> Yes, it looks like if it were an "unsigned int", we would have been >> okay. That looks like (essentially) what your patch does, but in a >> C++ idiom. I'll submit your patch and put a note out to the Windows >> guys to help test it. There's a

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

Michael Droettboom wrote: > Yes, it looks like if it were an "unsigned int", we would have been > okay. That looks like (essentially) what your patch does, but in a C++ > idiom. I'll submit your patch and put a note out to the Windows guys to > help test it. There's a good chance that if it c

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

Michael Droettboom wrote: > Yes, it looks like if it were an "unsigned int", we would have been > okay. That looks like (essentially) what your patch does, but in a C++ > idiom. I'll submit your patch and put a note out to the Windows guys to > help test it. There's a good chance that if it c

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

Yes, it looks like if it were an "unsigned int", we would have been okay. That looks like (essentially) what your patch does, but in a C++ idiom. I'll submit your patch and put a note out to the Windows guys to help test it. There's a good chance that if it compiles at all, it should work.

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

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. _tkagg.c

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

Hi, unfortunately 32-bit ;-) I tried digging around, but I don't know much about tcl/tk. Seeing a char string argv atol'ed into a pointer address left me with an uncomfortable feeling... Anyway her is the argv value Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

Ouch! The way that pointer is obtained is really weird (though I believe it is a common idiom in Tcl extensions): PyAggImagePhoto(ClientData clientdata, Tcl_Interp* interp, int argc, char **argv) { ... bboxo = (PyObject*)atol(argv[4]); if (bboxo != Py_None) {

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

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 = (gdb) p bbox $2 = (Bbox *) 0x7ffb (gdb) p bbox->_ll Cannot access memory at address 0x7ffb Cheers, Malte On 13/05/2008,

Re: [Matplotlib-users] tkinter segv under opensuse 10.3

This looks like the same symptoms as this (unresolved) bug here: http://sourceforge.net/tracker/index.php?func=detail&aid=1949982&group_id=80706&atid=560720 Your gdb backtrace reveals that you have debugging symbols in matplotlib, so we've got a little more information now. Thanks. Since this

[Matplotlib-users] tkinter segv under opensuse 10.3

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 P