Re: gtkmm-list Digest, Vol 33, Issue 54

["Arthur Maciel" <arthurmaciel gmail com>]

Just to let anyone know this was segfaulting due to a wrong
signal_activate() connected to a treeview.

Thanks, Paul! (he helped me)
Regards,
Arthur

> ---------- Mensagem encaminhada ----------
> From: "Arthur Maciel" <arthurmaciel gmail com>
> To: gtkmm-list <gtkmm-list gnome org>
> Date: Tue, 30 Jan 2007 00:18:37 -0200
> Subject: Segfault ending the program
> Dear Gtkmm team,
> my program uses libglademm to load its interface in a 'CitationWindow:
> public Gtk::Window' class.
>
> It is strangely segfaulting on quit (destroying the window through 'X'
> on the right corner). Valgrind output is:
>
> ----------------------------------------------------------------------------------------
> ==    at 0xFFFFFF68: ???
> ==    by 0x8057D35:
> sigc::adaptor_functor<sigc::bound_mem_functor0<void, CitationWindow>
> >::operator()() const (adaptor_trait.h:251)
> ==    by 0x8057D51:
> sigc::internal::slot_call0<sigc::bound_mem_functor0<void,
> CitationWindow>, void>::call_it(sigc::internal::slot_rep*)
> (slot.h:103)
> ==    by 0x43AE341:
> Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) (in
> /usr/lib/libglibmm-2.4.so.1.0.20)
> ==    by 0x4964049: g_cclosure_marshal_VOID__VOID (in
> /usr/lib/libgobject-2.0.so.0.1200.4)
> ==    by 0x4957CAC: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.1200.4)
> ==    by 0x49671EB: (within /usr/lib/libgobject-2.0.so.0.1200.4)
> ==    by 0x49683FA: g_signal_emit_valist (in
> /usr/lib/libgobject-2.0.so.0.1200.4)
> ==    by 0x49685B3: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.1200.4)
> ==    by 0x45D0C68: gtk_tree_view_remove_column (in
> /usr/lib/libgtk-x11-2.0.so.0.1000.6)
> ==    by 0x45DDD8E: (within /usr/lib/libgtk-x11-2.0.so.0.1000.6)
> ==    by 0x418D40B:
> Gtk::Container_Class::destroy_callback(_GtkObject*) (in
> /usr/lib/libgtkmm-2.4.so.1.0.25)
> ----------------------------------------------------------------------------------------
>
> Does it mean anything to anyone? I'll continue to debug, but if anyone
> has a solution (or its cause :-) I would appreciate knowing.
>
> Thanks.
> Regards,
> Arthur