Debugging Macros (Windows CE 5.0)
After debug zones are registered, use macro calls in the source code to output debugging messages.
Release and Debug configurations call different macros.
The following table describes macros called by Release configurations:
| Release Configuration Macro | Description |
|---|---|
| RETAILMSG(cond,printf_exp) | Conditionally displays the print message. |
| RETAILLED(cond,parms) | Conditionally outputs WORD values to the LED. |
| RETAILREGISTERZONES(hmod) | Enables debug zones for Release configurations. |
| ERRORMSG(cond,printf_exp) | Prints Error: File Line before the print message. |
Debug configurations use the three Release configuration macros and the following Debug macros. To enable debug macros, build a run-time image from a Debug configuration.
The following table describes macros called by Debug configurations:
| Debug Configuration Macro | Description |
|---|---|
| DEBUGREGISTER(hmod) | Enables debug zones for Debug configurations. |
| DEBUGMSG(cond,printf_exp) | Conditionally displays the print message. |
| DEBUGLED(cond,parms) | Conditionally outputs WORD values to the LED. |
| DEBUGCHK(expr) | Asserts the expression. If expr is FALSE, the macro calls DEBUGBREAK. |
| DEBUGZONE(zone_id) | Tests the mask bit in the current debug zone settings. You can use DEBUGZONE to turn debug zones on or off. |
See Also
Send Feedback on this topic to the authors