[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    Re: can't find the output of kDebug()
From:       Thomas_Lübking <thomas.luebking () gmail ! com>
Date:       2011-02-28 20:48:19
Message-ID: op.vrmr2sjk9bmiid () localhost ! localdomain
[Download RAW message or body]

Am 28.02.2011, 21:36 Uhr, schrieb Tsiapaliwkas Giorgos  
<terietor@gmail.com>:
run "kdebugdialog", filter for 1212, check it.

if you run "kdebugdialog --fullmode" you can do a lot more to it, that's  
why kDebug() is superior, but for simple testing during coding i just use  
qDebug as well - kDebug is supposed to remain in the code and be activated  
by fellow devs or end users for better debugging w/o compiling while not  
having everything spam your stderr all the time ;-)

Cheers,
Thomas
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin
[prev in list] [next in list] [prev in thread] [next in thread]