Re: activating --g-fatal-warning
- From: John Cupitt <jcupitt gmail com>
- To: Stefan Kost <kost imn htwk-leipzig de>
- Cc: gtk-app-devel-list gnome org
- Subject: Re: activating --g-fatal-warning
- Date: Fri, 24 Sep 2004 16:52:57 +0000
I have this near the start of my main():
#ifdef DEBUG_FATAL
/* Set masks for debugging ... stop on any problem.
*/
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 );
printf( "*** DEBUG_FATAL is on ... will abort() on first warning\n" );
#endif /*DEBUG_FATAL*/
then during testing I configure with -DDEBUG_FATAL
no doubt there's a better way :-/
On Fri, 24 Sep 2004 18:44:15 +0200, Stefan Kost
<kost imn htwk-leipzig de> wrote:
anyone knows what I have to do, that my app supports --g-fatal-warning for testing.
Apart wasn't there a way to control this via env vars. I cant find this
documented in the glib docs.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]