After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 320017 - Add G_DEBUG=fatal_criticals
Add G_DEBUG=fatal_criticals
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2005-10-27 22:05 UTC by Vincent Untz
Modified: 2005-11-04 19:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (3.50 KB, patch)
2005-10-27 22:06 UTC, Vincent Untz 		none Details | Review

Description Vincent Untz 2005-10-27 22:05:35 UTC 
In the hope of fixing all critical errors in application, I made a patch to add
G_DEBUG=fatal_criticals.

Patch was done against the 2.8 branch of glib.
Comment 1 Vincent Untz 2005-10-27 22:06:07 UTC 
Created attachment 53965 [details] [review]
patch
Comment 2 Emmanuele Bassi (:ebassi) 2005-10-27 22:20:43 UTC 
with this, we would have a "fatal-criticals" option blocking only criticals, and
a "fatal-warnings" blocking warnings *and* criticals.  I think that
"fatal-warnings" should do as the name implies, and block on g_warning(), while
"fatal-criticals" should block on g_critical().

this could be an API breakage - even though it's not strictly an API issue.
Comment 3 Matthias Clasen 2005-11-04 19:08:14 UTC 
Added to both branches

2005-11-04  Matthias Clasen  <mclasen@redhat.com>

        * glib/gdebug.h: add new GDebugFlag for fatal_criticals
        * glib/gmessages.c: (_g_debug_init): handle G_DEBUG=fatal_criticals,
        to help find critical warnings in applications.  (#320017,
        Vincent Untz)