Re: [trinity-devel] Reducing xession log spew

What is a good way to address xsession log spew? Many messages are helpful for debugging, but under normal usage clutters the xsession log. The messages should be toggled by the user as needed. Some examples: [tdeinit] Got EXEC_NEW.... [tdeinit] PID xxxx terminated. [tdeinit] Got SETENV.... [tdeinit] xxxx is executable and not a library. Launching with exec. When I look at these messages in kinit.cpp I notice they are fprintf(stderr) messages and many are conditional, based upon #ifndef NDEBUG. Is NDEBUG a compile-time variable (meaning "No debug"), or is this variable configurable during run-time as an environment variable? What options exist to reduce this spew? Darrell --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting