Gwenael Casaccio wrote: > Hi, > > Here is a simple tip if you've tried to launch gtk-blox more than 5 min ;) > without a crash you can launch like this : > > G_SLICE=always-malloc gst-blox
Hum, maybe G_SLICE=debug-blocks will help debugging it? The example in the documentation sounds like a likely case... "An example of a memory corruption scenario that cannot be reproduced with G_SLICE=always-malloc, but will be caught by G_SLICE=debug-blocks is as follows: void *slist = g_slist_alloc(); /* void* gives up type-safety */ g_list_free (slist); /* sizeof (GSList) != sizeof (GList) */ Paolo _______________________________________________ help-smalltalk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-smalltalk
