[Fwd: Re: GTK/GDK 1.2.2 crashes X]

[Ed Centanni <ecentan1 tampabay rr com>]

-------- Original Message --------
Subject: Re: GTK/GDK 1.2.2 crashes X
Date: Fri, 07 May 1999 22:32:41 +0000
From: Ed Centanni <ecentan1@tampabay.rr.com>
To: Owen Taylor <otaylor@redhat.com>
References: <37326AC3.39C2D6D0@tampabay.rr.com>
<ybed80c53hw.fsf@fresnel.labs.redhat.com>

Owen Taylor wrote:
> 
> Ed Centanni <ecentan1@tampabay.rr.com> writes:
> 
> > Running SuSE 5.3, gcc 2.7.2.1  libc.5.4.46.  I successfully compiled and
> > installed GLIB and GTK 1.2.2.  The testglib program works fine.  The
> > testdnd, testrgb and testgtk programs all crash X.  testinput,
> > testselection, and simple all run ok.   I stepped through in the
> > debugger and the crash occurs in different places in different
> > executables but consistently at the same place in the same executable --
> > usually on calling a function or returning from a function.  Calling
> > gdk_image_new in gdkrgb.c is one such example.  The X server XFREE
> > 3.3.3.1 SVGA server reports that it caught Signal 11.  (SIGSEGV)
> > Invalid memory reference.  My machine has been up for 40 days so I don't
> > think it's bad RAM.
> >
> > I've already tried re-compiling with -g -O0.  No change.  Did ldconfig.
> >
> > Compiled Glade and it crashes X too.  Any ideas/fixes/suggestions? I
> > really want to start using GTK.
> 
> To quote Jim Gettys:
> 
>  If GTK+ crashes X, then it is a bug in the X server.
>  If GTK+ crashes X, then it is a bug in the X server.
>  If GTK+ crashes X, then it is a bug in the X server.
> 
> It sounds like your crashes might have something to do
> with shared memory, so as a workaround you could try
> compiling GTK+ with --disable-shm, though it
> can slow the operation of programs down a lot.
> 
> Regards,
>                                         Owen

FANTASTIC!!!  the --disable-shm did it.  All the test programs work
now.  GLADE works now.  I expect that gIDE will too.  THANK YOU!

Ed Centanni