Filterin the debug output

[David Faure]

On Tuesday 23 October 2007, Andras Mantia wrote:
> On Tuesday 23 October 2007, Andreas Pakulat wrote:
> > On 23.10.07 13:41:43, Andras Mantia wrote:
> > > Hi,
> > >
> > >  Is it (technically) possible to filter the debug output as it was
> > > with with KDE3? kdebugdialog doesn't seem to work, and the amount
> > > of output printed to the console not only disturbs when debugging
> > > your own app, but makes things running much slower (see also
> > > Andreas's blog).
> >
> > kdebugdialog works just fine for me. I disabled most of kdevelop4's
> > debug output and its pretty little output now when I work on the
> > qmake or svn stuff :)
> 
> 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...

9016 and 4981 are PIDs, not debug areas!

Besides the klauncher/kdeinit4 output comes from other processes than your application;
I suggest running a full kde4 session, or running kdeinit4 in a different terminal from the one
where you are launching your application. It will already help a lot with not getting so much
output.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).