[Help-smalltalk] Re: Gtk Blox tip

[Gwenael Casaccio]

On Wednesday 25 February 2009 16:28:45 you wrote:
> 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

When I try to debug gst with gdb I've got this segfault :

Program received signal SIGSEGV, Segmentation fault.
0x00007fb251f16f0b in _gst_dictionary_add (dictionaryOOP=0x2b203f3d2030, 
associationOOP=0x2b203f3dc3d0) at dict.c:1877
1877          SET_ASSOCIATION_VALUE (associationOOP, value);

Gwenael