| Platform SDK: DirectX |
This topic pertains only to applications written in C++. For an introduction to programming for DirectX in Visual Basic, see Visual Basic Programming Topics.
To ensure that the debugger can find all the relevant symbolic information when using debug builds, locate the symbol files as follows:
| OS | Debugger | Location for .pdb file | Location for .dbg file |
|---|---|---|---|
| Windows 95 Windows 98 | Visual C++ | Same directory as binary | Same directory as binary |
| Windows NT Windows 2000 | Visual C++ | Same directory as binary | %SystemRoot%\Symbols\<binary extension>\ |
| Windows NT Windows 2000 | NTSD/KD | %SystemRoot%\Symbols\<binary extension>\ | %SystemRoot%\Symbols\<binary extension>\ |
Note When debugging with the Visual C++ development system on Microsoft® Windows NT®/Windows® 2000, do not use the WIN32API Splitsym development tool. WIN32API Splitsym copies private symbolic information from the <binary>.dbg file into the symbol directory under the binary extension (for example, %SystemRoot%\Symbols\Dll\ ), then deletes the original file from the binary directory. Visual C++ relies on finding a private symbolic information (<binary>.dbg) file in the same directory as the binary itself. Therefore, for debug builds, you must only copy the private symbolic information, and not delete it. This is an issue only when using Visual C++ with Windows NT/Windows 2000. Consult Visual C++ documentation and Windows 2000 Driver Development Kit (DDK) documentation for further debugging information.