How to Use Conditional Debug_Out & Trace_Out Debugging Strings

Last reviewed: July 10, 1996
Article ID: Q153386

The information in this article applies to:

Microsoft Windows Device Development Kit (DDK) for Windows 95

To avoid adding extra code to your source just to test or branch around debug message strings, you can use the built-in conditional macros in addition to the more plain Trace_Out and Debug_Out. An inspection of the DEBUG.H or DEBUG.INC files shows the following syntax:

Trace_Out## or Debug_Out## where ## is one of the following flags/conditions:

 S, C, A, AE, B, BE, E, Z, G, GE, L, LE, O,

NS,NC,NA,NAE,NB,NBE,NE,NZ,NG,NGE,NL,NLE,NO, EAXZ,EAXNZ,ECXZ,ECXNZ

example: Trace_OutC "carry set - function call failed with AX = #AX"

REFERENCES

Win95DDK\INC32\DEBUG.H Win95DDK\INC32\DEBUG.INC

Additional reference words:
KBCategory: kbprg kbhowto
KBSubcategory: ddkmisc

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 10, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.