Bug#242558: when loading attached file glade-2 segfaults

[Nicolas Chauvat]

> i did not manage to reduce the attached case any further. removing any
> element, even the label, is enough to avoid the core dumps that happens
> when clicking on "main_window" in glade's list of windows and dialogs.

running glade-2 via gdb I get :

$ gdb glade-2
(gdb) run
-----> I load the file, then click on main_window
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 6336)]
0x406e4598 in mallopt () from /lib/libc.so.6
(gdb) thread apply all bt

Thread 1 (Thread 16384 (LWP 6336)):
#0  0x406e4598 in mallopt () from /lib/libc.so.6
#1  0x406e30f0 in realloc () from /lib/libc.so.6
#2  0x4054b229 in g_realloc () from /usr/lib/libglib-2.0.so.0
#3  0x405387b7 in g_quark_to_string () from /usr/lib/libglib-2.0.so.0
#4  0x405384e6 in g_quark_from_string () from /usr/lib/libglib-2.0.so.0
#5  0x4029f1b7 in _gtk_style_peek_property_value ()
   from /usr/lib/libgtk-x11-2.0.so.0
#6  0x00000040 in ?? ()
#7  0xbfffe630 in ?? ()
#8  0x00000001 in ?? ()
#9  0x4029ef50 in gtk_style_set_background () from /usr/lib/libgtk-x11-2.0.so.0
Previous frame inner to this frame (corrupt stack?)
(gdb)


-- 
Nicolas Chauvat

logilab.fr - services en informatique avancée et gestion de connaissances