Why not always DEBUG=MSDEBUG?

[Daniel Morissette]

Frank Warmerdam wrote:
> 
> Can anyone think of a reason we wouldn't always enable use of debugging 
> output
> in mapserver?  

Here are the two reasons I can think of:

1- I am not 100% sure that all msDebug() calls are protected by an 
if(...debug) test. This would need to be verified prior to making your 
proposed change

2- Under IIS, stderr is merged with stdout so msDebug() just doesn't 
work there and enabling debug in that environment can (and often does!) 
result in malformed headers or corrupt output.


> It is a great frustration to me that many people with binary
> MapServer builds do not have MSDEBUG support enabled.  I'd like permission
> to make this non-optional.
> 
> I'm suggesting the --enable-debug / --disable-debug switches on the unix
> configure would just control -g.
> 

That would probably be a good idea as long as we also take care of the 
issues above.

BTW, bugs 709, 1333 and 1783 relate to this directly or indirectly and I 
had included a "cleanup of LOG/DEBUG output mechanisms" item covering 
them in the 5.0 roadmap.

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/