Dump Requirements and Limitations
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
.gif "Topic applies") |
|
Standard |
|
|
|
|
Pro and Team |
|
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
When you debug a dump, the machine on which you debug must have access to the PDB files and the binaries for the program. Visual Studio can cope with missing binaries for some modules, however, as long as it has enough modules to generate valid call stacks. The message "No matching binary found" appears in the Modules window. For more information, see Dump Module Loading.
If you load a minidump saved with the heap, Visual Studio can load the symbols even if the application binary is not found. Minidumps saved without the heap need to find the binary to load symbols. They are considerably smaller, however, which may be important if you have storage or bandwidth limits.
Managed minidumps cannot be debugged in the ordinary debugger windows. Instead, you must use a tool called SOS, run from the Immediate window. For more information, see How to: Use SOS.