Re: AboutDialog url hook not working?



> OK, so it's not just me then.  (by the way, I assume you mean
> gtk/src/aboutdialog.ccg?).

Yes.

> Something seems to be wrong somewhere though. Valgrind reports this when
>> I click on the link:
>>
>> ==27202==    at 0x4171B49:
>> SignalProxy_ActivateLink_gtk_callback(_GtkAboutDialog*, char const*,
>> void*) (slot_base.h:273)
>> ==27202==    by 0x43C4190: activate_url (gtkaboutdialog.c:1627)
>> ==27202==    by 0x48BBDF2: g_cclosure_marshal_VOID__VOID (gmarshal.c:77)
>> ==27202==    by 0x48AEEFE: g_closure_invoke (gclosure.c:490)
>> ==27202==    by 0x48BEEA4: signal_emit_unlocked_R (gsignal.c:2438)
>> ==27202==    by 0x48C09C9: g_signal_emit_valist (gsignal.c:2197)
>> ==27202==    by 0x48C0D18: g_signal_emit (gsignal.c:2241)
>> ==27202==    by 0x43DD991: gtk_button_clicked (gtkbutton.c:889)
>> ==27202==    by 0x43DFA22: gtk_real_button_released (gtkbutton.c:1484)
>> ==27202==    by 0x48BBDF2: g_cclosure_marshal_VOID__VOID (gmarshal.c:77)
>> ==27202==    by 0x48AE8CE: g_type_class_meta_marshal (gclosure.c:567)
>> ==27202==    by 0x48AEEFE: g_closure_invoke (gclosure.c:490)
>> ==27202==    by 0x48BF1FB: signal_emit_unlocked_R (gsignal.c:2368)
>> ==27202==    by 0x48C09C9: g_signal_emit_valist (gsignal.c:2197)
>> ==27202==    by 0x48C0D18: g_signal_emit (gsignal.c:2241)
>> ==27202==    by 0x43DD90E: gtk_button_released (gtkbutton.c:881)
>> ==27202==    by 0x43DEF28: gtk_button_button_release (gtkbutton.c:1377)
>> ==27202==    by 0x44B76D7: _gtk_marshal_BOOLEAN__BOXED
>> (gtkmarshalers.c:83)
>> ==27202==    by 0x48AE8CE: g_type_class_meta_marshal (gclosure.c:567)
>> ==27202==    by 0x48AEEFE: g_closure_invoke (gclosure.c:490)
>> ==27202==  Address 0x521B2FC is 4 bytes inside a block of size 44 free'd
>> ==27202==    at 0x401D268: operator delete(void*)
>> (vg_replace_malloc.c:246)
>> ==27202==    by 0x4756196: sigc::slot_base::~slot_base()
>> (slot_base.cc:101)
>> ==27202==    by 0x41BD28B: Gtk::Main::run(Gtk::Window&) (slot.h:422)
>> ==27202==    by 0x8049CB3: main
>> (in /home/murrayc/cvs/gnome216/gtkmm/a.out)
>
> So nothing happens after it reaches
> SignalProxy_ActivateLink_gtk_callback?  Is that what you're trying to
> show?  I'm not completely sure what I'm looking for here...

The slot (or the useful part of it) seems to have been deleted, before the
point at which the GTK+ callback tries to use it. Valgrind errors usually
have two parts - where it went wrong, and where caused that.

Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]