RE: stop on Gtk-WARNING
The same for GLib-GObject-WARNINGs and other similar ones. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boncek, John Sent: Monday, October 17, 2005 11:33 AM To: gtk-app-devel-list@gnome.org Subject: stop on Gtk-WARNING When a GTK app gets Gtk-WARNINGs without actually stopping, it can be hard to determine exactly where they're coming from. Is there a way to tell GTK to stop immediately on such a warning? This would allow using a debugger to localize the first warning much more easily. ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: stop on Gtk-WARNING
there is an argument you can pass in to the application at invocation that does this. i think it is --g-fatal-warnings (eg ./foo --g-fatal-warnings). -tim ** http://mail.gnome.org/archives/gtk-devel-list/1998-August/msg00088.htmlBoncek, John wrote: http://mail.gnome.org/archives/gtk-devel-list/1998-August/msg00088.html The same for GLib-GObject-WARNINGs and other similar ones. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boncek, John Sent: Monday, October 17, 2005 11:33 AM To: gtk-app-devel-list@gnome.org Subject: stop on Gtk-WARNING When a GTK app gets Gtk-WARNINGs without actually stopping, it can be hard to determine exactly where they're coming from. Is there a way to tell GTK to stop immediately on such a warning? This would allow using a debugger to localize the first warning much more easily. ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: stop on Gtk-WARNING
On 10/17/05, Boncek, John [EMAIL PROTECTED] wrote: When a GTK app gets Gtk-WARNINGs without actually stopping, it can be hard to determine exactly where they're coming from. Is there a way to tell GTK to stop immediately on such a warning? This would allow using a debugger to localize the first warning much more easily. I have something like this near the start of my main(): #ifdef DEBUG g_log_set_always_fatal( G_LOG_FLAG_RECURSION | G_LOG_FLAG_FATAL | G_LOG_LEVEL_ERROR | G_LOG_LEVEL_CRITICAL | G_LOG_LEVEL_WARNING ); #endif /*DEBUG*/ Alternatively, you can pass --g-fatal-warnings as a command-line argument to any gtk program. Either technique will cause your program to abort() on the first warning, so you can get a stack trace if you run in a debugger. See http://developer.gnome.org/doc/API/2.0/glib/glib-Message-Logging.html J ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
