Filterin the debug output

Andreas Pakulat apaku at gmx.de
Tue Oct 23 13:05:15 BST 2007


On 23.10.07 13:22:41, Thiago Macieira wrote:
> Em Tuesday 23 October 2007 13:05:29 Andras Mantia escreveu:
> > On Tuesday 23 October 2007, Boudewijn Rempt wrote:
> > > That's the problem: for unknown debug codes, the default is visible.
> > > The list with codes needs to be expanded.
> >
> > Yeah, and that's a problem. For example 9016 outputs KHTMLPluginKTTSD
> > info. But in kdebug.areas:
> >
> > #9016        kdevelop (perl support)
> >
> > So in the past it was part of kdevelop (as all areas from 9000-9039 and
> > 9500-9510).
> >
> > I think this has to be cleaned up.
> >
> > Andras
> 
> Note that kdebugrc is shared with KDE 3, so you can't simply overtake debug 
> areas.

What do you mean with overtake? 90xx was never used in kde3 by anything
but kdevelop, so if you just mean that khmlpluginkttsd shouldn't have
used the 90xx range number then yes I agree.

The only thing that might be problematic is that IIRC some numbers
changed from kdev3->kdev4, i.e. if you switch of language/cpp in kdev3
you might get no output from the kdev-shell library when running kdev4.

Andreas

-- 
Your supervisor is thinking about you.




More information about the kde-core-devel mailing list