| Type | recommended |
| Title | OSL_TRACE only active if OSL_DEBUG_LEVEL>1 |
| Posted by | [EMAIL PROTECTED] |
| Affected | ,all |
| Effective from | SRC680 CWS kso13 |
Summary
OSL_TRACE only active if OSL_DEBUG_LEVEL>1
Description
Formerly, OSL_TRACE was active if OSL_DEBUG_LEVEL was greater than
zero. (true for non-pro builds, even if not compiled with debug info).
This led to several (annoying) trace messages when working with a
non-pro build. OSL_TRACE output is not supposed to be a hint for
malfunctions; thus it is not of common interest.
Starting with integration of CWS kso13, OSL_TRACE will be only active
in case OSL_DEBUG_LEVEL is greater than one (true if compiling with
debug information, regardless of pro or non-pro build).
Please check whether you're using OSL_TRACE (output not of common
interest; no issue needs to be filed) where you actually want to use
OSL_ASSERT (output indicates an unpredicted situation; issue should be
filed) and change your code accordingly.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
