Dear visitor, welcome to KDE-Forum.org.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
kdDebug confirmation question
Hello,
I just want a confirmation to what I think I understood about kdDebug (after some search on the web and on this forum) : are the debug mechanisms really activable only if kdelibs are compiled with --enable-debug=full ?
My problem is that I'm developping a little KDE game that still have bugs and I'd like to use kdDebug to display debug messages but I really don't want to recompile all kdelibs for this little program.
Thank you in advance.
Kleag
No, I don't think so.
Run kdebugdialog an check if the category for generic is enabled.
Cheers,
_
Qt/KDE Developer
Debian User
No, kdDebug() will work anyway. It's just printing your message to the standard-error output channel. Use it instead of "cerr" in your KDE applications ;-)
Using --enable-debug with ./configure is a completely different story. Likely it will include a lot of debugging-information in the compiled binary (done with the -g switch of g++/gcc). This makes binary files huge and slow, but you can print a complete stack dump, and a crash dump returns the exact line numbers of the source code, etc..
Working on
KMess, a MSN Messenger client for Linux/KDE.
This post has been edited 3 times, last edit by "vdboor" (Nov 16th 2004, 11:02pm)
Problem solved
Your hint solved my problem on one machine. I am not for the moment able to check it on the machine where I was not able to see my debug messages. But I'm sure it's OK.
Thanks to both of you