Filterin the debug output

Kevin Krammer kevin.krammer at gmx.at
Tue Oct 23 12:19:56 BST 2007


On Tuesday 23 October 2007, Andras Mantia wrote:

> Well, it doesn't work completely. :) I was wrong, indeed it disabled
> some debug output, but for example after disabling ALL debug outputs, i
> still get this when loading a page in konqueror:
> konqueror(9016) KHTMLPluginKTTSD::KHTMLPluginKTTSD:
> KHTMLPLuginKTTSD::KHTMLPluginKTTSD: KTrader did not find KTTSD.
> klauncher(4981)/kio (KLauncher) KLauncher::requestSlave: KLauncher:
> launching new slave  "kio_file"  with protocol= "file"  args=
> ("file",
> "local:/home/andris/.kde4/socket-stein/klauncherMT4981.slave-socket",
> "local:/home/andris/.kde4/socket-stein/konquerorqV9016.slave-socket")
> kdeinit4: Got EXEC_NEW 'kio_file' from launcher.
> kdeinit4: preparing to launch
>
> (and other from 9016 and 4981 areas).
> Hm, this areas do not even appear in kdebugdialog...

I think those numbers are the PID of the process the output is coming from, 
not the debug area.
Probably those outputs are from kDebug() lines, i.e. usage without debug area.

Cheers.
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071023/4fa9f4c3/attachment.sig>


More information about the kde-core-devel mailing list