Share via


Dumps

This topic applies to:

Edition

Visual Basic

C#

C++

Web Developer

Express

Topic does not apply Topic does not apply Topic applies Topic 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.

Dump files, previously called crash dumps, allow you to save program information for debugging later. The Visual Studio debugger can load dump files created by Visual Studio or by other programs that generate dump files. You can also save dump files, but only from native applications.

Dumps can be especially useful if you are testing a program on a machine that does not have source files or PDB Files (C+). When a crash occurs, you can save a dump file on that machine and debug it later on the build machine or another machine that has the source files and PDBs.

How to Create a Dump

There are several ways to create a dump:

Debugging a Dump

The Visual Studio debugger can read dump files that contain information about managed code, unmanaged code, or a mixture of both.

For native code, you can use the normal debugger windows to view dump information.

For managed code, you cannot use the normal debugger windows to view dump information. Instead, you must use a tool called SOS that displays information in the Command window. For information, see SOS.

The following sections contain additional information about debugging a dump:

See Also

Concepts

Debugger Security

Other Resources

Debugger Roadmap