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 61752 - GtkCTree crash in widget tree window
GtkCTree crash in widget tree window
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: Other
1.2.x
Other other
: Low critical
: ---
Assigned To: gtk-bugs
Damon Chaplin
: 57253 61756 67139 70114 94040 109061 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-10-04 18:48 UTC by runger
Modified: 2011-02-04 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description runger 2001-10-04 18:48:53 UTC 
Package: glade
Severity: normal
Version: 0.6.2
Synopsis: Glade crashed, unexpectedly....
Bugzilla-Product: glade
Bugzilla-Component: general

Description:
A segmentation fault occured. I was not doing anything specific (I had just moved my mouse from the Clipboard preview window to the widget tree window). I had just done quite a bit of editing (an lost it all!!) with fairly complicated nesting to my components, and many copy/paste operations.
I realize this bug description is not very useful, but perhaps the stack trace will tell you something...

Richie


Debugging Information:

(no debugging symbols found)...0x404a48c9 in __wait4 () from /lib/libc.so.6

+ Trace 11132

  • #0 __wait4
    from /lib/libc.so.6
  • #1 ??
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 127
  • #4 draw_row
    at gtkctree.c line 1665
  • #5 draw_rows
    at gtkclist.c line 5976
  • #6 vadjustment_value_changed
    at gtkclist.c line 6224
  • #7 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #8 gtk_handlers_run
    at gtksignal.c line 1917
  • #9 gtk_signal_real_emit
    at gtksignal.c line 1477
  • #10 gtk_signal_emit_by_name
    at gtksignal.c line 618
  • #11 gtk_range_default_vmotion
    at gtkrange.c line 682
  • #12 gtk_range_motion_notify
    at gtkrange.c line 1029
  • #13 gtk_marshal_BOOL__POINTER
    at gtkmarshal.c line 28
  • #14 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #15 gtk_signal_emit
    at gtksignal.c line 552
  • #16 gtk_widget_event
    at gtkwidget.c line 2864
  • #17 gtk_propagate_event
    at gtkmain.c line 1378
  • #18 gtk_main_do_event
    at gtkmain.c line 818
  • #19 gdk_event_dispatch
    at gdkevents.c line 2139
  • #20 g_main_dispatch
    at gmain.c line 656
  • #21 g_main_iterate
    at gmain.c line 877
  • #22 g_main_run
    at gmain.c line 935
  • #23 gtk_main
    at gtkmain.c line 524
  • #24 main
  • #25 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 92
  • #0 __wait4
    from /lib/libc.so.6
  • #1 ??
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 127
  • #4 draw_row
    at gtkctree.c line 1665
  • #5 draw_rows
    at gtkclist.c line 5976
  • #6 vadjustment_value_changed
    at gtkclist.c line 6224
  • #7 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-10-04 14:48 -------

The original reporter (runger@cim.mcgill.ca) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, damon@ximian.com.
Comment 1 Damon Chaplin 2001-10-05 22:56:05 UTC 
*** Bug 61756 has been marked as a duplicate of this bug. ***
Comment 2 Damon Chaplin 2001-10-05 22:57:19 UTC 
As you can see in the stack trace, the crash occurs in GtkCTree code.
So I'm not sure it is a bug in Glade itself.

Though I'll try to track it down at some point.
Comment 3 Damon Chaplin 2002-01-22 02:06:17 UTC 
*** Bug 67139 has been marked as a duplicate of this bug. ***
Comment 4 Damon Chaplin 2002-01-22 02:07:47 UTC 
*** Bug 57253 has been marked as a duplicate of this bug. ***
Comment 5 Luis Villa 2002-01-28 16:35:57 UTC 
Is this GNOME2 relevant, damon?
Comment 6 Luis Villa 2002-01-28 16:58:18 UTC 
GNOME2-related spam. search on 'luis doing GNOME2 work' to filter these out.
Comment 7 Damon Chaplin 2002-01-28 23:36:26 UTC 
Yes, this bug will probably still be there in the GNOME2 version.

We should try to use GtkTreeView for the widget tree instead of
GtkCTree. That would probably fix it.
Comment 8 Damon Chaplin 2002-02-21 01:26:09 UTC 
*** Bug 70114 has been marked as a duplicate of this bug. ***
Comment 9 Damon Chaplin 2002-04-10 18:38:35 UTC 
We now use a GtkTreeView for GTK+2, rather than the GtkCTree, so this
shouldn't be relevant there. So I'm removing the GNOME2 keyword.
Comment 10 Damon Chaplin 2002-04-22 17:07:21 UTC 
Moving to GTK+, as it is probably a GtkCTree bug.
Comment 11 Owen Taylor 2002-04-23 20:56:00 UTC 
This could easily be a Glade bug, since it hasn't been
reported elsewhere. Without reproduction instructions,
or at least symbols in the backtrace, I don't think
there is much possibility of making progress on this.
Comment 12 Damon Chaplin 2002-10-06 16:37:52 UTC 
*** Bug 94040 has been marked as a duplicate of this bug. ***
Comment 13 Damon Chaplin 2003-04-01 13:43:37 UTC 
*** Bug 109061 has been marked as a duplicate of this bug. ***
Comment 14 Owen Taylor 2004-02-24 00:52:18 UTC 
No 1.2.11 is planned, so closing all 1.2.11 specific bugs.
Comment 15 Owen Taylor 2004-02-24 14:07:17 UTC 
*Really* close all 1.2.11 bugs, instead of just adding a comment...