David Gowers wrote:
>> The what's new document for each release is a good resource for these
>> kinds of problems, especially its porting section:
>> http://docs.python.org/whatsnew/porting.html

The last two items on that page seem to be the more likely candidates that 
could cause problems. I don't see any calls to *_Malloc() or *_Free(). There 
are a number of calls to g_free(). If any of them are being called on items 
that were not allocated by a glib routine that could be the cause of the crash.

That page has also made me aware of at least one change needed for 64-bit 



http://www.ve3syb.ca/           |"What are we going to do today, Borg?"
Owner of Elecraft K2 #2172      |"Same thing we always do, Pinkutus:
                                 |  Try to assimilate the world!"
#include <disclaimer/favourite> |              -Pinkutus & the Borg
Gimp-developer mailing list

Reply via email to