GtkICQ bug
- From: Daniel Burrows <Daniel_Burrows brown edu>
- To: gnome-list gnome org
- Subject: GtkICQ bug
- Date: Wed, 27 Jan 1999 14:56:51 -0500
GtkICQ crashes if you try to do two searches simultaneously. The specific
problem occurs when I click "Search" in the second dialog and manifests itself
as follows:
Gtk-WARNING **: invalid class type `(unknown)' in cast to `GtkEntry'
Gtk-CRITICAL **: file gtkentry.c: line 482 (gtk_entry_get_text): assertion `GTK_IS_ENTRY (entry)' failed.
Program received signal SIGSEGV, Segmentation fault.
0x404437a9 in ()
(gdb) ba
#0 0x404437a9 in ()
#1 0x80541ea in begin_search (widget=0x80d0de8, entries=0x80703d0)
at /usr/include/stdlib.h:156
#2 0x4012b25d in gtk_marshal_NONE__NONE (object=0x80d0de8,
func=0x80541c0 <begin_search>, func_data=0x80703d0, args=0xbfffec30)
at gtkmarshal.c:365
#3 0x400ed7a5 in gtk_handlers_run (handlers=0x808b138, signal=0xbfffebec,
object=0x80d0de8, params=0xbfffec30, after=0) at gtksignal.c:1877
#4 0x400ecbe3 in gtk_signal_real_emit (object=0x80d0de8, signal_id=68,
params=0xbfffec30) at gtksignal.c:1445
#5 0x400eabbf in gtk_signal_emit (object=0x80d0de8, signal_id=68)
at gtksignal.c:528
#6 0x4005e2b8 in gtk_button_clicked (button=0x80d0de8) at gtkbutton.c:330
#7 0x4005f9c9 in gtk_real_button_released (button=0x80d0de8)
at gtkbutton.c:842
#8 0x4012b25d in gtk_marshal_NONE__NONE (object=0x80d0de8,
func=0x4005f930 <gtk_real_button_released>, func_data=0x0, args=0xbfffef6c)
at gtkmarshal.c:365
#9 0x400ecab3 in gtk_signal_real_emit (object=0x80d0de8, signal_id=67,
params=0xbfffef6c) at gtksignal.c:1408
#10 0x400eabbf in gtk_signal_emit (object=0x80d0de8, signal_id=67)
at gtksignal.c:528
#11 0x4005e1f8 in gtk_button_released (button=0x80d0de8) at gtkbutton.c:321
#12 0x4005f342 in gtk_button_button_release (widget=0x80d0de8, event=0x80e7d08)
at gtkbutton.c:702
#13 0x4012ae29 in gtk_marshal_BOOL__POINTER (object=0x80d0de8,
func=0x4005f280 <gtk_button_button_release>, func_data=0x0,
args=0xbffff2bc) at gtkmarshal.c:32
#14 0x400ecc1c in gtk_signal_real_emit (object=0x80d0de8, signal_id=27,
params=0xbffff2bc) at gtksignal.c:1460
#15 0x400eabbf in gtk_signal_emit (object=0x80d0de8, signal_id=27)
at gtksignal.c:528
#16 0x40121d38 in gtk_widget_event (widget=0x80d0de8, event=0x80e7d08)
at gtkwidget.c:2732
#17 0x400befb2 in gtk_propagate_event (widget=0x80d0de8, event=0x80e7d08)
at gtkmain.c:1237
#18 0x400be148 in gtk_main_do_event (event=0x80e7d08) at gtkmain.c:694
#19 0x401668fb in gdk_event_dispatch (source_data=0x0,
current_time=0xbffff620, user_data=0x0) at gdkevents.c:2063
#20 0x40193d32 in g_main_dispatch (current_time=0xbffff620) at gmain.c:640
#21 0x40194221 in g_main_iterate (block=1, dispatch=1) at gmain.c:829
#22 0x401943d1 in g_main_run (loop=0x80cd030) at gmain.c:887
#23 0x400bdc6b in gtk_main () at gtkmain.c:456
#24 0x4041dd35 in applet_widget_gtk_main () at applet-widget.c:868
#25 0x805c876 in main (argc=1, argv=0xbffffc34) at gtkicq.c:1390
It looks like the problem happens in Gtk+ code somewhere, maybe something
is being freed and invalidated by the handler for one of the searches but
still referenced by the other one?
Daniel
PGP signature
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]