[Glade-users] glade Segmentation Fault

[Damon Chaplin]

On Thu, 2004-03-18 at 09:45, Damon Chaplin wrote:
> On Wed, 2004-03-17 at 18:23, Jonathan Lane wrote:
> 
> > #0  0x4030dd1e in mallopt () from /lib/libc.so.6
> > #1  0x4030cd33 in malloc () from /lib/libc.so.6
> > #2  0x40189095 in g_malloc () from /usr/lib/libglib-1.2.so.0
> 
> It looks like it might be memory corruption, which is often difficult to
> track down.
> 
> If someone could track it down to a specific widget that would help a
> lot.
> 
> If you have valgrind installed that may spot the problem.
> 
> You can also try setting the "MALLOC_CHECK_" environment variable to 2,
> in Debian. That turns on some checking of malloc() calls. See malloc(3).

I've just tried using valgrind 1.9.6 and setting MALLOC_CHECK_ but they
didn't find any problems, unfortunately.

Are you using a binary package of Glade? You could try compiling Glade
from source and seeing if that makes any difference.

Damon