Re: Trapping Glib critical error messages

2019-08-08 Thread Phil Wolff via gtkmm-list
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

Re: Trapping Glib critical error messages

2019-08-08 Thread Jens Georg
On Do, Aug 8, 2019 at 9:12 AM, Kjell Ahlstedt via gtkmm-list wrote: Or, in gdb: break g_log You might want to set a condition then, though, because some things are quite debug-chatty ___ gtkmm-list mailing list gtkmm-list@gnome.org

Re: Trapping Glib critical error messages

2019-08-08 Thread Kjell Ahlstedt via gtkmm-list
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, mailto:gtkmm-list@gnome.org>> wrote: GLib-GObject-CRITICAL **: 15:30:09.453:

Re: Trapping Glib critical error messages

2019-08-07 Thread 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, wrote: > GLib-GObject-CRITICAL **: 15:30:09.453: g_object_unref: assertion > 'G_IS_OBJECT (object)' failed > GLib-GIO-CRITICAL **: 15:30:09.453: >

Trapping Glib critical error messages

2019-08-07 Thread Phil Wolff via gtkmm-list
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