CJ Kucera wrote:
> Okay, I've got a reproducible testcase of this available up here:
> http://apocalyptech.com/pygtk-zlib/
>
> I'm no longer *totally* convinced that it's a zlib issue... zlib's call
> actually returns a valid string, and the error happens later in the app.
Hello, again, list. O
CJ Kucera wrote:
> Okay, I've got a reproducible testcase of this available up here:
> http://apocalyptech.com/pygtk-zlib/
Hello, two brief notes here:
1) Someone on the PyGTK list mentioned that I should really be using
StringIO instead of my own hacky attempt at one, in there, and of course
he
bieff...@gmail.com wrote:
> If you have worked with C/C++, you know that memory-related bugs can
> be very tricky.
> More than once - working with C code - I had crashes that disappeared
> if I just added
> a 'printf', because the memory allocation scheme changed and the
> memory corrupted was not
CJ Kucera wrote:
bieff...@gmail.com wrote:
It looks like some of the C extension you are using is causing a
segfault or similar in python
interpreter (or it could be a bug in the interpreter itself, but it is
a lot less likely).
Okay... I assume by "C extension" you'd include the PyGTK stuff,
bieff...@gmail.com wrote:
> It looks like some of the C extension you are using is causing a
> segfault or similar in python
> interpreter (or it could be a bug in the interpreter itself, but it is
> a lot less likely).
Okay... I assume by "C extension" you'd include the PyGTK stuff, right?
(ie:
