Re: Call to g_print() causes Seg Fault
- From: Marc Fearby <marc fearby com>
- To: gtk-list redhat com
- Subject: Re: Call to g_print() causes Seg Fault
- Date: Sat, 31 Jul 1999 02:37:03 +0000
Ted Roth wrote:
> On Tue, 27 Jul 1999, Allan Black wrote:
>
> > Does this work:
> >
> > /* example-start base base.c */
> >
> > int main( int argc, char *argv[] )
> > {
> > g_print ("Hello World\n");
> > return (0);
> > }
> >
> > /* example ends here */
> >
> > ???
> >
> > Allan
>
> I had the same problem last night. I had just upgraded from Redhat 5.2 to
> 6.0. My glib-1.2.3 rpms where built on the 5.2 system. I rebuilt the rpms
> for RH6.0 and did a `rpm -Uvh --force` to install the glib and gtk+ stuff
> and the problem went away. Most likely something in the glibc-2.0 ->
> glibc-2.1 conversion from the RH5.2 -> RH6.0 switch.
>
> Ted Roth
I'm running libc6 2.1.1-1 and have no other problems. I ran "dpkg -i
--force-overwrite" on the following packages from this GNOME mirror site:
ftp://mirror.aarnet.edu.au/pub/gnome/gnome-1.0/debian/dists/slink/main/binary-i386
libgtk-1.2_1.2.3-0.slink1_i386.deb
libgtk-1.2-dev_1.2.3-0.slink1.i386.deb
libglib1.2_1.2.3-0.slink1.i386.deb
libglib1.2-dev_1.2.3-0.slink1.i386.deb
A recompile of the above source works fine - but it still SEGV's when I run
it. I wouldn't have expected to have to do this on a Linux system, but do I
have to completely un-install everything to do with GTK and re-install it? It
would seem rather drastic :-(
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]