> Hi,
>
> I encountered a matter with the debug viking's feature. We use g_debug
> function. But in glib 2.32, the g_debug behavior changed and all DEBUG
> messages are discarded, unless G_MESSAGES_DEBUG is set. So, "viking
> -d" no more work as its design was to mute DEBUG messages when "-d" is
> not set.
>
> Do you have idea to restore "viking -d" behavior?
>
Hmm, annoying!
What about:
1. Replace all g_debug() calls to viking_debug()
2. Create new function viking_debug() function in globals.c
3. Make viking_debug() call g_debug() for glib versions < 2.32, otherwise just
call g_print()
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
