On 11 Jan., 14:34, kevin <[email protected]> wrote:
> On Jan 11, 2:44 am, kfj <[email protected]> wrote:
>
> > Hi!
> I found it this morning, it's hardcoded in the util.h or utils.h
> file. Not in front of my home machine to tell you which, just
> remember it was name one of those. Just the DEBUG_TRACE, etc defines
> are the blank ones to turn it off. I commented out the DEBUG_ ones
> and uncommented the blank ones and it's not printing out all the DEBUG
> info now.
Thank you for that! It's in hugin.hg/src/hugin_base/hugin_utils/
utils.h as you say. I suppose it's this section:
//#ifdef DEBUG
// debug trace
#define DEBUG_TRACE(msg) { std::cerr << "TRACE " << DEBUG_HEADER
<< msg << std::endl; }
// low level debug info
#define DEBUG_DEBUG(msg) { std::cerr << "DEBUG " << DEBUG_HEADER
<< msg << std::endl; }
// informational debug message,
#define DEBUG_INFO(msg) { std::cerr << "INFO " << DEBUG_HEADER <<
msg << std::endl; }
// major change/operation should use this
#define DEBUG_NOTICE(msg) { std::cerr << "NOTICE " << DEBUG_HEADER
<< msg << std::endl; }
//#else
// #define DEBUG_TRACE(msg)
// #define DEBUG_DEBUG(msg)
// #define DEBUG_INFO(msg)
// #define DEBUG_NOTICE(msg)
//#endif
Someone has just commented out the switch and hardcoded debug messages
on.
Grrr....
But at least it made me notice another problem I would have never seen
if this hadn't happened, so it wasn't all just a big waste of time
(but mainly... :(
Kay
--
You received this message because you are subscribed to the Google Groups
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx