Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

Dump Requirements and Limitations

This topic applies to:

Edition

Visual Basic

C#

C++

Web Developer

Express

Topic does not applyTopic does not applyTopic appliesTopic does not apply

Standard

Topic applies

Topic applies

Topic applies

Topic does not apply

Pro and Team

Topic applies

Topic applies

Topic applies

Topic does not apply

Table legend:

Topic applies

Applies

Topic does not apply

Does not apply

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.

Community Additions

ADD
Show:
© 2015 Microsoft