Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Symbol files hold various data that while not essential for running the binaries, can be useful for debugging. Symbols can include the symbol name, symbol type (if applicable), symbol store address (or register), and any parent or child symbols. Examples of symbols include variable names (local and global), functions, and any entry point into a module.
The debugger gets its information about symbols from symbol files located on the local file system or loaded from a remote symbol server. When you use a symbol server, the debugger automatically uses the correct version of the symbol file to match the module in the target.
Locate symbols for Windows debuggers
Symbols for the Windows debuggers are available from a public symbol server over the internet. Windows debuggers include WinDbg (a kernel-mode and user-mode debugger), the kernel debugger (KD), Microsoft Console Debugger (CDB), and Microsoft NT Symbolic Debugger (NTSD).
For user-mode debugging, you need symbols for your target application.
For kernel-mode debugging, you need symbols for the driver you're debugging and also the Windows public symbols.
You can load symbols automatically with the .symfix command, which sets the symbol store path. To run the command, you need access to the internet while your debugger is running. Next, use the .reload command to reload the module and symbols.
To learn more about symbols, including WinDbg support for Portable PDB symbols, see the following articles:
Access symbols while debugging
The following articles describe how to access symbols during a debugging session. They also explain how to control the debugger's symbol options and symbol matching.
- Microsoft public symbol server
- Windows symbol packages for debugging
- Symbol path for Windows debuggers
Tip
To configure your debugger to access symbols for your own programs and for Windows, get started quickly by reading Symbol path and Microsoft public symbol server. Use the !sym noisy command to display more detail as symbols are loaded to troubleshoot issues with symbols. For more information, see the !sym command reference.