suson at TuckerEnergy.com
Fri Feb 4 01:31:27 UTC 2005
Many thanks! I ran kdebugdialog, hit apply, and was then able to get
output w/ kdDebug() or kdDebug(0). Is there any way to add custom areas?
Jens Dagerbo wrote:
>On Thursday 03 February 2005 01.36, Steven Suson wrote:
>> Hopefully, this will not be too off topic (there is the possibility
>>that the problem I'm having is KDevelop specific). I am attempting to
>>use kdDebug, albeit unsuccessfully. Here's the code in question:
>>kdDebug() << k_funcinfo << ": Sonde Type " <<
>>toolItem->SCRData()->getSondeType() << " at depth " << item->depth() <<
>> I stepped through this in the debugger to assure that it was being
>>executed, and in fact it is. My project is being compiled debug (i.e.
>>NDEBUG is not being defined by the compile command). Yet, I cannot seem
>>to get anything output. I've tried both running the program from within
>>KDevelop (where there is no output within the Application tab), from
>>within KDevelop's Konsole tab, and from a plain Konsole shell prompt.
>>None of these yield any output.
>>Any clues as to how to get this working will be greatly appreciated.
>> I'm using KDevelop 3.1.2, KDE 3.3.1, Qt 3.3.3, gcc 3.2.2
>Most likely the debug area simply isn't configured to give any output. Run
>'kdebugdialog' to turn on or off debug areas.
>kdDebug() is the same as kdDebug(0), btw. You can trace to a specific area
>(number) to be able to then easily filter out the traces you are interested
>in (using kdebugdialog).
>to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
More information about the KDevelop