Re: Trapping Glib critical error messages

Daniel Boles via gtkmm-list <[email protected]> Wed, 7 Aug 2019 23:58:49 +0100

Newsgroups	gmane.comp.gnome.gtkmm
Message-ID	<CAKChMKPDVzb13c3xMtu547_MHBk2C=eXPDwTfuOCqEZOqJf5GA@mail.gmail.com>

run with G_DEBUG=fatal-criticals or -warnings or etc to taste


On Wed, 7 Aug 2019, 23:50 Phil Wolff via gtkmm-list, <[email protected]>
wrote:

> GLib-GObject-CRITICAL **: 15:30:09.453: g_object_unref: assertion
> 'G_IS_OBJECT (object)' failed
> GLib-GIO-CRITICAL **: 15:30:09.453:
> g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION
> (connection)' failed
>
> I'm getting these messages seemingly at random in a program I'm working
> on. Can someone tell me the Glib g_xxxx function that prints these
> messages so I can trap them to get a traceback?
>
> _______________________________________________
> gtkmm-list mailing list
> [email protected]
> https://mail.gnome.org/mailman/listinfo/gtkmm-list
>

_______________________________________________
gtkmm-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gtkmm-list