[9045] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Gdk segfault messages
daemon@ATHENA.MIT.EDU (Blake)
Sun Oct 4 16:29:01 1998
From: Blake <laertes@stab.gemma.com>
To: gtk-list@redhat.com
Date: Sun, 4 Oct 1998 15:33:40 -0600 (GMT+6)
In-Reply-To: <ybeaf3cm5au.fsf@fresnel.labs.redhat.com> from "Owen Taylor" at Oct 4, 98 04:38:01 pm
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
> >
> > > > Using the new gtk-1.1.2 anf glib-1.1.3 along with gnome-0.30 I'm getting
> > > > the following message running gnothello:
> > > > Gdk-Message:
> > > > ** ERROR **: sigsegv caught
> > > I can not reproduce this problem myself. Are you sure you dont have
> > > any older gtk+ libraries installed on the system lying around or at
> > > the time you compiled the code?
> >
> > I have the same libraries and the same problem.
> > Note that I hadn't this problem with gtk-1.1.
> >
> > BTW:
> >
> > domi:~ > gnome-help-browser
> > Gdk-Message:
> > ** ERROR **: sigsegv caught
> >
> > I get this message from various GNOME apps, since I use gtk-1.1.2.
>
> This is most likely not a problem with GDK at all - GDK just
> installs the segfault handler, so puts its name on the message.
>
> You can find out where it is segfaulting by running it under
> gdb, and making a backtrace:
>
> gdb gnothello
> (gdb) r
> (gdb) where
>
> Regards,
> Owen
I think it is gnorba or CORBA somehow. I have a problem myself with
gnothello since I dinked up CORBA.
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
