4 Sep
2012
4 Sep
'12
2:33 p.m.
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
4 Sep
4 Sep
2:38 p.m.
New subject: [trinity-devel] Reducing xession log spew
On 4 September 2012 17:33, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
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
is it related at all to the kdedebugdialog options? just an idea
2:40 p.m.
New subject: [trinity-devel] Reducing xession log spew
is it related at all to the kdedebugdialog options?
just an idea
Not that I see. The messages are fprintf(stderr) and not kdedebug (xxxx) messages. As
I'm not a C++ coder I'm looking at examples to see whether some of these can be
converted, although I don't know the correct kdedebug category.
Darrell
5:58 p.m.
New subject: [trinity-devel] Reducing xession log spew
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.
I'm testing a patch with three of the fprintf messages converted to kdDebug. One
fprintf message has me stumped. I would appreciate help converting this message to
kdDebug:
fprintf(stderr, "[tdeinit] Got %s '%s' from %s.\n",
(request_header.cmd == LAUNCHER_EXEC ? "EXEC" :
(request_header.cmd == LAUNCHER_EXT_EXEC ? "EXT_EXEC" :
(request_header.cmd == LAUNCHER_EXEC_NEW ? "EXEC_NEW" :
(request_header.cmd == LAUNCHER_SHELL ? "SHELL" : "KWRAPPER"
)))),
name, launcher ? "launcher" : "socket" );
Thanks.
By the way, in the est patch I created a new kdDebug area: 182 tdecore(kinit).
Darrell
5 Sep
5 Sep
1:07 a.m.
New subject: [trinity-devel] Reducing xession log spew
On Wednesday 05 September 2012 03:58:16 Darrell Anderson wrote:
The simplest way:
QString msg;
msg.sprintf("[tdeinit] Got %s '%s' from %s.\n",
(request_header.cmd == LAUNCHER_EXEC ? "EXEC" :
(request_header.cmd == LAUNCHER_EXT_EXEC ? "EXT_EXEC" :
(request_header.cmd == LAUNCHER_EXEC_NEW ? "EXEC_NEW" :
(request_header.cmd == LAUNCHER_SHELL ? "SHELL" : "KWRAPPER" )))),
name, launcher ? "launcher" : "socket" );
kdDebug() << msg;
--
Serghei
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.
I'm testing a patch with three of the fprintf messages converted to
kdDebug. One fprintf message has me stumped. I would appreciate help
converting this message to kdDebug:
fprintf(stderr, "[tdeinit] Got %s '%s' from %s.\n",
(request_header.cmd == LAUNCHER_EXEC ? "EXEC" :
(request_header.cmd == LAUNCHER_EXT_EXEC ? "EXT_EXEC" :
(request_header.cmd == LAUNCHER_EXEC_NEW ? "EXEC_NEW" :
(request_header.cmd == LAUNCHER_SHELL ? "SHELL" : "KWRAPPER"
)))),
name, launcher ? "launcher" : "socket" );
Thanks.
12:47 p.m.
New subject: [trinity-devel] Reducing xession log spew
The simplest way:
QString msg;
msg.sprintf("[tdeinit] Got %s '%s' from %s.\n",
(request_header.cmd == LAUNCHER_EXEC ? "EXEC" :
(request_header.cmd == LAUNCHER_EXT_EXEC ? "EXT_EXEC" :
(request_header.cmd == LAUNCHER_EXEC_NEW ? "EXEC_NEW" :
(request_header.cmd == LAUNCHER_SHELL ? "SHELL" : "KWRAPPER"
)))),
name, launcher ? "launcher" : "socket" );
kdDebug() << msg;
Thank you!
Now the remaining problem is I can't get the messages to appear at all. :(
Darrell
12:50 p.m.
New subject: [trinity-devel] Reducing xession log spew
On Wednesday 05 September 2012 22:47:52 Darrell Anderson wrote:
I think this can be controlled by kdebugdialog.
The simplest
way:
QString msg;
msg.sprintf("[tdeinit] Got %s '%s' from %s.\n",
(request_header.cmd == LAUNCHER_EXEC ? "EXEC" :
(request_header.cmd == LAUNCHER_EXT_EXEC ? "EXT_EXEC" :
(request_header.cmd == LAUNCHER_EXEC_NEW ? "EXEC_NEW" :
(request_header.cmd == LAUNCHER_SHELL ? "SHELL" : "KWRAPPER"
)))),
name, launcher ? "launcher" : "socket" );
kdDebug() << msg;
Thank you!
Now the remaining problem is I can't get the messages to appear at all. :( Darrell
--
Serghei
12:56 p.m.
New subject: [trinity-devel] Reducing xession log spew
Now the
remaining problem is I can't get the messages
to appear at all. :(
I think this can be controlled by kdebugdialog.
1:03 p.m.
New subject: [trinity-devel] Reducing xession log spew
On Wednesday 05 September 2012 22:56:28 Darrell Anderson wrote:
Yes, but I haven't figured out the process works.
I set the following in the global kdebugrc:
# KInit debug info off
[182]
InfoOutput=4
That part seems to be working because the messages no longer appear. When I
run kdebugdialog and enable the new 182 area, those new messages still do
not appear.
I tried changing the global kdebugrc:
# KInit debug info off
[182]
InfoOutput=2
I restarted Trinity. Still no 182 messages.
Darrell
If i'm not wrong, kdDebug() means "0". Or you use kdDebug(182)?
--
Serghei
Now the remaining problem is I can't get the
messages
to appear at all. :(
I think this can be controlled by kdebugdialog.
4269
days inactive
4270
days old
9 comments
3 participants
participants (3)
-
Calvin Morrison -
Darrell Anderson -
Serghei Amelian