Bug#333118: Bug#333119: gcc-4.0: Segfaulting code generated for gtkboard-0.11pre0

["R.Ramkumar" <ramk@cse.iitm.ernet.in>]

> Why are you not using gcc-4.0 4.0.2-2, the current version of gcc-4.0 in
> unstable?

I generally go with the testing packages.. should I be reporting the
bugs only with the unstable version?

> What is the last version of the compiler that you are able to use to
> successfully compile this code in this environment with no other changes?

gcc-3.3 3.3.6-7 has no problems whatsoever (I needn't have to make
changes like removing static, but I guess this is an intended
feature in gcc-4.0, this is not the first package I have seen not
compiling due to this) and no segfault occurs.

> Have you confirmed that this bug exists in gcc-snapshot?

I have, now. Segfaults still. However, the bt is slightly different.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208879424 (LWP 9790)]
0x0809c7ff in __PRETTY_FUNCTION__.8049 ()
(gdb) bt
#0  0x0809c7ff in __PRETTY_FUNCTION__.8049 ()
#1  0x081a63a0 in ?? ()
#2  0x08180ff8 in ?? ()
#3  0xbfa39a88 in ?? ()
#4  0x4120a728 in ?? () from /usr/lib/libgobject-2.0.so.0
#5  0xbfa39cfc in ?? ()
#6  0x4120a728 in ?? () from /usr/lib/libgobject-2.0.so.0
#7  0xbfa39a88 in ?? ()
#8  0x48aa823c in gtk_item_factory_get_type () from /usr/lib/libgtk-x11-2.0.so.0
Previous frame inner to this frame (corrupt stack?)

Ramkumar.

-- 
96.31% of all statistics are fiction.