[Bug 227089] KDE runtime libraries are by default in noisy debug mode to stdout/stderr

[Oliver Henshaw]

https://bugs.kde.org/show_bug.cgi?id=227089


Oliver Henshaw <yoho_ahoy at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yoho_ahoy at hotmail.com




--- Comment #5 from Oliver Henshaw <yoho_ahoy hotmail com>  2010-03-04 18:28:08 ---
With everything unticked in kdebugdialog, there is still a lot of kde-related
stuff in .xsession-errors. I had a little dig around to see why and came up
with a couple of findings:

* Sometimes this is deliberate - e.g. kdelibs/kinit/kinit.cpp:launch uses
fprintf rather than the kdebug infrastructure.

* Sometimes this is accidental - some code is using debug areas that aren't
found in /usr/share/config/kdebug.areas - and so the debug console spew remains
on.

A couple of examples are

*
kdebase/runtime/kglobalaccel/globalshortcutsregistry.cpp:GlobalShortcutsRegistry::registerKey
 A debug area is not specified here, but KDE_DEFAULT_DEBUG_AREA=181 was set in
CMakeLists.txt. This debug area was a holdover from past times and it looks
like the problem has been fixed in trunk.

* kdebase/runtime/knotify/knotify.cpp:KNotify::event
 hard-codes a debug area of 300. This isn't currently defined in kdebug.areas
but I haven't looked to see whether it's a typo or code rot or what.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.