how to debug ?

[f***@promotux.it]

I have a segmentation fault on glade3.7.3 compiled from source.
Some devel can write please wich steps to do for the right trace ?

For now i have just that but i think it is not enough

(glade-3:31430): GLib-GObject-WARNING **:
/tmp/buildd/glib2.0-2.27.91/./gobject/gtype.c:4197: type id `0' is invalid

(glade-3:31430): GLib-GObject-WARNING **: can't peek value table for
type `<invalid>' which is not currently referenced
Segmentation fault


thanks

[Johannes Schmid]

Hi!

Post by f***@promotux.it
I have a segmentation fault on glade3.7.3 compiled from source.
Some devel can write please wich steps to do for the right trace ?

# gdb glade3
(gdb) run --g-fatal-warnings
.
.
.
(gdb) bt
<copy the output and report a bug with it on bugzilla.gnome.org>

(gdb) quit


Does that happen on startup, btw? If yes, it could be a corrupted
installation.

Thanks,
Johannes

[Archit Baweja]

Hey Francesco,

If you've compiled the glade source yourself, make sure you've compiled it
with debug information. Usually that involves compiling with the GCC -g
flag. Try the following

export CFLAGS='-g' ; ./configure

With that GDB will show you proper names in stack traces instead of hex
values of addresses of functions, routines etc.

And you're right, what you have is not enough. All that part says is that
the Gtk+ subsystem got a NULL value instead of a valid Gtk+ object id. So
probably some funtion/routine higher up in the call stack that is faulty.

Hope that helps,
Archit

Post by f***@promotux.it
I have a segmentation fault on glade3.7.3 compiled from source.
Some devel can write please wich steps to do for the right trace ?
For now i have just that but i think it is not enough
/tmp/buildd/glib2.0-2.27.91/./gobject/gtype.c:4197: type id `0' is invalid
(glade-3:31430): GLib-GObject-WARNING **: can't peek value table for
type `<invalid>' which is not currently referenced
Segmentation fault
thanks
--
_______________________________________________
http://lists.ximian.com/mailman/listinfo/glade-devel

[Tristan Van Berkom]

Post by Archit Baweja
Hey Francesco,
If you've compiled the glade source yourself, make sure you've
compiled it with debug information. Usually that involves compiling
with the GCC -g flag. Try the following
export CFLAGS='-g' ; ./configure

you can also just ./configure --enable-debug to get the debug flags.

Cheers,
-Tristan

Post by Archit Baweja
With that GDB will show you proper names in stack traces instead of
hex values of addresses of functions, routines etc.
And you're right, what you have is not enough. All that part says is
that the Gtk+ subsystem got a NULL value instead of a valid Gtk+
object id. So probably some funtion/routine higher up in the call
stack that is faulty.
Hope that helps,
Archit
I have a segmentation fault on glade3.7.3 compiled from source.
Some devel can write please wich steps to do for the right trace ?
For now i have just that but i think it is not enough
/tmp/buildd/glib2.0-2.27.91/./gobject/gtype.c:4197: type id `0' is invalid
(glade-3:31430): GLib-GObject-WARNING **: can't peek value table for
type `<invalid>' which is not currently referenced
Segmentation fault
thanks
--
_______________________________________________
http://lists.ximian.com/mailman/listinfo/glade-devel
_______________________________________________
http://lists.ximian.com/mailman/listinfo/glade-devel

_______________________________________________
Glade-devel maillist - Glade-***@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/glade-devel

[f***@promotux.it]

Post by Tristan Van Berkom

Post by Archit Baweja
Hey Francesco,
If you've compiled the glade source yourself, make sure you've
compiled it with debug information. Usually that involves compiling
with the GCC -g flag. Try the following
export CFLAGS='-g' ; ./configure

you can also just ./configure --enable-debug to get the debug flags.
Cheers,
-Tristan

Post by Archit Baweja
With that GDB will show you proper names in stack traces instead of
hex values of addresses of functions, routines etc.
And you're right, what you have is not enough. All that part says is
that the Gtk+ subsystem got a NULL value instead of a valid Gtk+
object id. So probably some funtion/routine higher up in the call
stack that is faulty.
Hope that helps,
Archit
I have a segmentation fault on glade3.7.3 compiled from source.
Some devel can write please wich steps to do for the right trace ?
For now i have just that but i think it is not enough
/tmp/buildd/glib2.0-2.27.91/./gobject/gtype.c:4197: type id
`0' is invalid
(glade-3:31430): GLib-GObject-WARNING **: can't peek value table for
type `<invalid>' which is not currently referenced
Segmentation fault
thanks
--
_______________________________________________
http://lists.ximian.com/mailman/listinfo/glade-devel
_______________________________________________
http://lists.ximian.com/mailman/listinfo/glade-devel

i am sorry, here i am again.

i tried on natty with a deb 3.7.3 package and it segfaulted also.

so i cloned the git with the last five hours old commit from Tristan
and compiled with the flag but no incresed debug for now.

i used gdb and i have this now:

(glade-3:4274): GladeUI-CRITICAL **: glade_project_model_get_value:
assertion `VALID_ITER (model, iter)' failed

(glade-3:4274): GLib-GObject-WARNING **:
/tmp/buildd/glib2.0-2.27.91/./gobject/gtype.c:4197: type id `0' is invalid

(glade-3:4274): GLib-GObject-WARNING **: can't peek value table for type
`<invalid>' which is not currently referenced

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff76ff169 in gtk_tree_model_get_valist () from
/usr/lib/libgtk-x11-2.0.so.0

is it more usefull ?

can i add a bug report with this ?

The problem is that i can't attach my gladefile because of a python
catalog that glade needs to open the file but i dont think it is
related with the segfault

thanks

[f***@promotux.it]

Post by f***@promotux.it

Post by Tristan Van Berkom

Post by Archit Baweja
Hey Francesco,
If you've compiled the glade source yourself, make sure you've
compiled it with debug information. Usually that involves compiling
with the GCC -g flag. Try the following
export CFLAGS='-g' ; ./configure

you can also just ./configure --enable-debug to get the debug flags.
Cheers,
-Tristan

Post by Archit Baweja
With that GDB will show you proper names in stack traces instead of
hex values of addresses of functions, routines etc.
And you're right, what you have is not enough. All that part says is
that the Gtk+ subsystem got a NULL value instead of a valid Gtk+
object id. So probably some funtion/routine higher up in the call
stack that is faulty.
Hope that helps,
Archit
I have a segmentation fault on glade3.7.3 compiled from source.
Some devel can write please wich steps to do for the right trace ?
For now i have just that but i think it is not enough
/tmp/buildd/glib2.0-2.27.91/./gobject/gtype.c:4197: type id
`0' is invalid
(glade-3:31430): GLib-GObject-WARNING **: can't peek value
table for
type `<invalid>' which is not currently referenced
Segmentation fault
thanks
--
_______________________________________________
http://lists.ximian.com/mailman/listinfo/glade-devel
_______________________________________________
http://lists.ximian.com/mailman/listinfo/glade-devel

i am sorry, here i am again.
i tried on natty with a deb 3.7.3 package and it segfaulted also.
so i cloned the git with the last five hours old commit from Tristan
and compiled with the flag but no incresed debug for now.
assertion `VALID_ITER (model, iter)' failed
/tmp/buildd/glib2.0-2.27.91/./gobject/gtype.c:4197: type id `0' is invalid
(glade-3:4274): GLib-GObject-WARNING **: can't peek value table for type
`<invalid>' which is not currently referenced
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff76ff169 in gtk_tree_model_get_valist () from
/usr/lib/libgtk-x11-2.0.so.0
is it more usefull ?
can i add a bug report with this ?
The problem is that i can't attach my gladefile because of a python
catalog that glade needs to open the file but i dont think it is
related with the segfault
thanks

(gdb) bt
#0 0x00007ffff76ff169 in gtk_tree_model_get_valist () from
/usr/lib/libgtk-x11-2.0.so.0
#1 0x00007ffff76ff449 in gtk_tree_model_get () from
/usr/lib/libgtk-x11-2.0.so.0
#2 0x00007ffff7b60bbd in selection_foreach_func (model=0x7c3cd0,
path=0x264fbc0, iter=0x7fffffffd520,
selection=0x7fffffffd5b0) at glade-inspector.c:585
#3 0x00007ffff770b0bb in gtk_tree_selection_selected_foreach () from
/usr/lib/libgtk-x11-2.0.so.0
#4 0x00007ffff7b60c28 in selection_changed_cb (selection=0x20fe500,
inspector=0x2227470)
at glade-inspector.c:600
#5 0x00007ffff57c933e in g_closure_invoke () from
/usr/lib/libgobject-2.0.so.0
#6 0x00007ffff57e23b9 in ?? () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff57e3b36 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#8 0x00007ffff57e4363 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#9 0x00007ffff7722d9a in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x00007ffff772d991 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x00007ffff760fc23 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x00007ffff57c933e in g_closure_invoke () from
/usr/lib/libgobject-2.0.so.0
#13 0x00007ffff57e1ff2 in ?? () from /usr/lib/libgobject-2.0.so.0
#14 0x00007ffff57e397c in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#15 0x00007ffff57e4363 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#16 0x00007ffff7741c7f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#17 0x00007ffff7606913 in gtk_propagate_event () from
/usr/lib/libgtk-x11-2.0.so.0
#18 0x00007ffff7607acb in gtk_main_do_event () from
/usr/lib/libgtk-x11-2.0.so.0
#19 0x00007ffff725713c in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#20 0x00007ffff4f08362 in g_main_context_dispatch () from
/lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#21 0x00007ffff4f0ca28 in ?? () from /lib/libglib-2.0.so.0
#22 0x00007ffff4f0cf35 in g_main_loop_run () from /lib/libglib-2.0.so.0
#23 0x00007ffff7607f87 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#24 0x00000000004117a5 in main (argc=1, argv=0x7fffffffe388) at main.c:185

is this usefull ?