After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 1502 - gtk+ Core Dump
gtk+ Core Dump
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: .General
1.2.x
Other other
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 2598 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 1999-06-16 17:40 UTC by brian.aingworth
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description brian.aingworth 2001-01-27 19:46:28 UTC
Problem: general
Package: gtk+
Version: 1.2.3

We get a core dump upon invocation of any program compiled with gtk.
Here is the output of gdb running on Solaris 7:

aingwort@[/u/aingwort/tools_source/gtk/gtk+-1.2.3/examples/helloworld]gdb

helloworld
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for
details.
GDB 4.15.1 (sparc-sun-solaris2.4), Copyright 1995 Free Software
Foundation,
Inc...
(gdb) run
Starting program:
/export/home/aingwort/tools_source/gtk/gtk+-1.2.3/examples/helloworld/hellow

orld
"/usr/platform/SUNW,Ultra-Enterprise/lib/libc_psr.so.1": not in
executable
format: File format not recognized.
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
gtk_type_name_hash (key=0x300610 <Address 0x300610 out of bounds>) at
gtktypeutils.c:917
917   while (*key)
(gdb)


--
***************************************************************************

* Brian Aingworth
* Lockheed Martin Federal Systems
* Owego,NY, 13827
* e-mail: brian.aingworth@lmco.com
*
*               Only my own opinions are offered.
*
***************************************************************************




------- Additional Comments From otaylor@redhat.com 1999-06-16 13:59:38 ----

Subject: Re: Bug#1502: gtk+ Core Dump
From: Owen Taylor <otaylor@redhat.com>
To: 1502@bugs.gnome.org
Message-Id: <ybe4sk8c9h1.fsf@fresnel.labs.redhat.com>
Date: 16 Jun 1999 13:59:38 -0400


Brian Aingworth <brian.aingworth@lmco.com> writes:

> We get a core dump upon invocation of any program compiled with gtk.
> Here is the output of gdb running on Solaris 7:
> 
> aingwort@[/u/aingwort/tools_source/gtk/gtk+-1.2.3/examples/helloworld]gdb
> 
> helloworld
> GDB is free software and you are welcome to distribute copies of it
>  under certain conditions; type "show copying" to see the conditions.
> There is absolutely no warranty for GDB; type "show warranty" for
> details.
> GDB 4.15.1 (sparc-sun-solaris2.4), Copyright 1995 Free Software
> Foundation,
> Inc...
> (gdb) run
> Starting program:
> /export/home/aingwort/tools_source/gtk/gtk+-1.2.3/examples/helloworld/hellow
> 
> orld
> "/usr/platform/SUNW,Ultra-Enterprise/lib/libc_psr.so.1": not in
> executable
> format: File format not recognized.
> (gdb) continue
> Continuing.
> 
> Program received signal SIGSEGV, Segmentation fault.
> gtk_type_name_hash (key=0x300610 <Address 0x300610 out of bounds>) at
> gtktypeutils.c:917
> 917   while (*key)
> (gdb)

Can provide a backtrace at this point? ('where' in gdb)

Thanks,
                                        Owen




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 14:46 -------
This bug was previously known as bug 1502 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=1502
Originally filed under the gtk+ product and general component.

The original reporter (brian.aingworth@lmco.com) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, gtk-bugs@gtk.org.

Comment 1 Owen Taylor 2001-02-01 00:57:51 UTC
*** Bug 2598 has been marked as a duplicate of this bug. ***
Comment 2 Owen Taylor 2001-02-01 01:04:52 UTC
2598 provides the backtrace.

I think this must be a code generation bug in the compiler - 
since the codepath is trivially correct, and the problem
doesn't occur on with other setups.

(neither bug specifies what compiler, though the use of gdb
indicates it's probably gcc.)

It may have to do with the inline keyword on
gtk_type_register_intern().