Re: kdebug defaults/build options
Bruce Sass wrote:
> On August 10, 2011 02:13:49 PM Xavier Brochard wrote:
>> Bruce Sass wrote:
>> >> 2. At times I've been annoyed by the number of spam messages
>> >> kwrite/kate leave on the console when run that way. Looking into it,
>> >> these messages are kDebug outputs. The kde techbase suggests [1] this
>> >> output is intended to be disabled in releases. Would you have any
>> >> objections to doing this in the future, with kwrite at least? There's
>> >> not many programs I've had problems with, but I do wince when running
>> >> kwrite from a console every so often.
>>
>> >> [1]:
>>
http://techbase.kde.org/Development/FAQs/Debugging_FAQ#Is_there_a_preferred
>>
>> >> _way_to_print_debug_output_on_stderr.3F
>> >
>> > My work-around to this problem is to tack "&>/dev/null &" onto the end
>> > of all cmdline issued KDE commands...
>>
>> An easier approach is to simply run kdebugdialog then select/deselect the
>> apps that you want to not send debug output
>
> If I ever run Stable's KDE I probably will--assuming Debian hasn't
> already--
No, but I don't know what is the good choice:
On one Debian squeeze install, I've got a .xsession-errors which grows very
fast (a few hours) to 320 Go. It was on a multi users system and was very
problematic. It was purely a kde problem (with Nepomuk/Akonadi), which I
solved. But, if debug output were disable, it might be possible that I would
never know about it.
regards
xavier
Reply to: