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 61756 - Glade crashed again, damn it!
Glade crashed again, damn it!
Status: RESOLVED DUPLICATE of bug 61752
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2001-10-04 19:42 UTC by runger
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description runger 2001-10-04 19:43:23 UTC 
Package: glade
Severity: normal
Version: 0.6.2
Synopsis: Glade crashed again, damn it!
Bugzilla-Product: glade
Bugzilla-Component: general

Description:
Again, I cannot give much useful context...
I was editing the same glade file as in my last bug report, 1 h ago...
This time I was dragging the mouse withing the widget tree window when I got a segmentation fault...




Debugging Information:

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

+ Trace 11138

  • #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 15:43 -------

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:06 UTC 
Looks like the same bug in both stack traces.

*** This bug has been marked as a duplicate of 61752 ***