Debugging Build Utility Products

  • Article

In the build environment for the Windows Driver Kit (WDK), you can always debug what you build. Regardless of how you build by using the Build utility, the symbol files that are used for debugging will be created.

You can control the type and amount of symbolic information with the NTDEBUG environment variable, and the NTDEBUGTYPE and MSC_OPTIMIZATION macros.

The build environment automatically sets the following environment variables. These allow you to perform source debugging or assembly debugging on your code.

NTDEBUG=ntsd
NTDEBUGTYPE=both
MSC_OPTIMIZATION=/Odi

For more information, see Debugging Drivers.

Note   Most other build programs do not automatically generate symbol files. In the Visual Studio build environment, you can choose between a "debug" build and a "retail" build; only the debug build includes symbol files.

 

 

Send comments about this topic to Microsoft

Build date: 5/3/2011