Dump Files

This topic applies to:


Visual Basic




Web Developer


Topic does not apply Topic does not apply Topic does not apply Topic does not apply Topic does not apply

Pro, Premium, and Ultimate

Topic applies

Topic applies

Topic does not apply

Topic applies

Topic applies

Dump files, previously called crash dumps, allow you to save program information for debugging a later time. Dump files can be especially useful when you are testing a program on a computer that does not have source or symbol files. When a crash occurs, you can save a dump file and debug it later, either on the build computer or on another computer that has the source files and debugging symbols.

The dump files that are saved and opened by Visual Studio use a file format called minidump. Visual Studio can save minidump files with or without heap information.

The Visual Studio 2010 debugger can save minidump files for either managed or native code. The debugger can load dump files that were created by Visual Studio 2010 or by other programs that save files in the minidump format.

Creating a Dump File

There are several ways to create and save a dump file:

Using a Dump File

The Visual Studio 2010 debugger can read dump files that contain information about managed code, unmanaged code, or a mixture of both. You can debug both native and managed dumps using the normal debugging windows.

The following sections contain additional information about how to work with a dump:

See Also


Debugger Security

Other Resources

Debugger Roadmap