GLib-GObject-CRITICAL warnings

Question

I'm confused by these two warnings. Can anyone explain how I might have come about triggering them, and how they would be able to be debugged in gdb?

(gtkworkbook:24668): GLib-GObject-CRITICAL **: g_cclosure_new: assertion `callback_func != NULL' failed

(gtkworkbook:24668): GLib-GObject-CRITICAL **: g_signal_connect_closure_by_id: assertion `closure != NULL' failed

I get these all the time... quite annoying.

Zifre
– Zifre

2009-07-16 17:15:06 +00:00
Commented Jul 16, 2009 at 17:15 — Zifre
– Zifre, Commented Jul 16, 2009 at 17:15
What usually was the cause of the problem?

John Bellone
– John Bellone

2009-07-16 17:24:37 +00:00
Commented Jul 16, 2009 at 17:24 — John Bellone
– John Bellone, Commented Jul 16, 2009 at 17:24

mattwright · Accepted Answer · 2009-07-16 19:10:01Z

3

One thing you can try is pass in --g-fatal-warnings to Gtk::Main, this will cause warnings to assert. You can attach with gdb and maybe figure out some more detail about where this is failing.

answered Jul 16, 2009 at 19:10

mattwright

7888 silver badges8 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

John Bellone · Accepted Answer · 2009-07-17 13:24:19Z

I found the problem.

This code was ported from an original implementation in C, and I had a requirement before to use an array of function pointers to call the functions inside of a shared library. Although this [seemed] to work at the time once I actually started using them it was not the case. I am a little stumped on why its not working, but I was able to centralized the problem to the following piece of code.

gtk_signal_connect (GTK_OBJECT (plugin()->workbook()->gtk_workbook), "switch-page",
 (GtkSignalFunc)this->signals[NOTEBOOK_SWITCHPAGE], plugin->workbook());

Was changed to the following:

gtk_signal_connect (GTK_OBJECT (plugin()->workbook()->gtk_workbook), "switch-page",
 (GtkSignalFunc)signal_gtknotebook_switchpage, plugin->workbook());

Now, the code compiles and I am not getting any nasty errors. I think this is the answer!

Collectives™ on Stack Overflow

GLib-GObject-CRITICAL warnings

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related