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 78734 - segmentation fault in glade with drv_z42/z42tool (glade Crash at 163.117.145.39)
segmentation fault in glade with drv_z42/z42tool (glade Crash at 163.117.145.39)
Status: VERIFIED INCOMPLETE
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2002-04-15 08:17 UTC by rcasero
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rcasero 2002-04-15 08:17:56 UTC
Package: glade
Version: 0.6.4
Severity: 

>Synopsis: segmentation fault in glade with drv_z42/z42tool
>Class: sw-bug
System: laptop Kapok 2700c GNU/Linux Debian Woody libc6 2.2.5-4 (KDE2 or Gnome)

>Description:
z42tool is an application to align the cartridges of the printer Lexmark Z42, that comes with the driver found at http://www.xs4all.nl/~pastolk/. The tool source code has to be generated with glade, but when  doing 'construct', it gives a segmentation fault.

>How-To-Repeat:
cp drv_z42-0.3.4.tar.gz /tmp/
cd /tmp/
tar xvzf drv_z42-0.3.4.tar.gz
cd drv_z42/z42tool/
glade z42tool.glade &

(GUI) -> I press button "Construir" ("Build")

I get the error (I translate):
"glade" application (process 3243) has failed due to a fatal error (segmentation fault)




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-15 04:17 -------

The original reporter (rcasero@tsc.uc3m.es) 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 2002-04-16 20:44:19 UTC
I can't reproduce.

Can you attach a stack trace?


(The files should really be included in the tarball, so you don't
need to generate them with Glade.)
Comment 2 rcasero 2002-04-17 11:19:38 UTC
I'm sorry, I do not know how to generate a stack trace, but if you 
tell me how, I'll do it.
Comment 3 Damon Chaplin 2002-04-17 16:38:56 UTC
The easiest way is to run Glade in gdb, with 'gdb glade'.

Then generate the code so Glade crashes.

Then type 'bt' into the gdb window and it should print out a stack
trace.
Comment 4 rcasero 2002-04-19 08:23:23 UTC
Here's the stack trace you asked for. I must say, I've been having
problems with gnome in woody. Maybe that's the problem. E.g., I had
problems whith bonobo and some other packets when doing apt-get upgrade.

Program received signal SIGSEGV, Segmentation fault.
0x0806d909 in gb_widget_write_standard_source ()
(gdb) bt
  • #0 gb_widget_write_standard_source
  • #1 gb_hbox_new
  • #2 gb_widget_write_source
  • #3 gb_dialog_new
  • #4 gb_widget_write_source
  • #5 source_write
  • #6 glade_project_foreach_component
  • #7 source_write
  • #8 source_write
  • #9 source_write
  • #10 source_write
  • #11 glade_project_write_source
  • #12 glade_project_write_source
  • #13 glade_project_window_open_project
  • #14 glade_project_window_open_project
  • #15 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #16 gtk_signal_remove_emission_hook
    from /usr/lib/libgtk-1.2.so.0
  • #17 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #18 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #19 gtk_button_clicked
    from /usr/lib/libgtk-1.2.so.0
  • #20 gtk_button_get_relief
    from /usr/lib/libgtk-1.2.so.0
  • #21 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #22 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #23 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #24 gtk_button_released
    from /usr/lib/libgtk-1.2.so.0
  • #25 gtk_button_get_relief
    from /usr/lib/libgtk-1.2.so.0
  • #26 gtk_marshal_BOOL__POINTER
    from /usr/lib/libgtk-1.2.so.0
  • #27 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #28 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #29 gtk_widget_event
    from /usr/lib/libgtk-1.2.so.0
  • #30 gtk_propagate_event
    from /usr/lib/libgtk-1.2.so.0
  • #31 gtk_main_do_event
    from /usr/lib/libgtk-1.2.so.0
  • #32 gdk_wm_protocols_filter
    from /usr/lib/libgdk-1.2.so.0
  • #33 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #34 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #35 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #36 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #37 bonobo_main
    from /usr/lib/libbonobo.so.2
  • #38 main
  • #39 __libc_start_main
    from /lib/libc.so.6

Comment 5 Ben FrantzDale 2002-11-08 00:05:59 UTC
This is a unique stack trace. Can it be reproduced with a recent version?
Comment 6 Vincent Noel 2004-10-06 17:06:07 UTC
According to the stack trace, this bug occurred in a Gnome 1.x application.
Please upgrade to a newer and improved version of gnome, e.g. 2.8.