On 7/23/07, Kevin Cozens <kevin@xxxxxxxxx> wrote: > 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 > machines. > > -- > Cheers! > > Kevin. Was trying to investigate this further. It turns out that current SVN of pygegl will not compile: gegl.override: In function '_wrap_gegl_node_render': gegl.override:332: error: incompatible type for argument 2 of 'gegl_node_blit' gegl.override:332: error: incompatible type for argument 3 of 'gegl_node_blit' gegl.override:332: warning: passing argument 6 of 'gegl_node_blit' makes integer from pointer without a cast gegl.override: In function 'pygegl_register_classes': gegl.override:139: warning: dereferencing type-punned pointer will break strict-aliasing rules due to a change in the blitting api. Tiny patch is attached to fix it. The crash I originally reported still happens; none of the g_free calls seem to be freeing anything other than glib allocated memory. _______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
