David Ripton wrote: > Utterly terrifying that something as fundamental as zlib would be broken > on a platform as common as Windows.
Actually, I suppose it's still *possible* that it's a Cairo function which is getting in the way, instead, and the zlib change merely brings it to light? I'm not quite sure anymore. Here's a reproducible script and data: http://apocalyptech.com/pygtk-zlib/ Would someone mind taking a look quick and let me know if this is something I should submit to Python or PyGTK's tracker? Thanks... On an XP system of mine, removing "import os" and "import sys" will "fix" the problem. On a win2k machine I can get rid of those imports and still see the crash, though. It's definitely a memory-clobbering bug of some sort, I'm just not quite sure where. Thanks! -CJ -- WOW: Flemmy | "Happiness isn't good enough for me! I [email protected] | demand euphoria!" 24.24.2.3171 | - Calvin _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
