Re: Trapping Glib critical error messages
Phil Wolff via gtkmm-list <[email protected]>
| Newsgroups | gmane.comp.gnome.gtkmm |
|---|---|
| Message-ID | <[email protected]> |
That's the one I need. Thanks! On 8/8/19 12:12 AM, Kjell Ahlstedt wrote: Or, in gdb: break g_log Den 2019-08-08 kl. 00:58, skrev Daniel Boles via gtkmm-list: 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? -- What was that about a rising tide lifting all boats? What if you don't have a boat? — Eugene Robinson _______________________________________________ gtkmm-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gtkmm-list