This documentation is archived and is not being maintained.

Using SOS

To view dump information on managed code, you must use a tool called SOS that runs in the Command window. SOS accepts commands from the Command window and uses the Command window to display information. It does not use the other debugger windows, such as the Call Stack or Locals window.

For unmanaged code, dump information does appear in all the usual debugger windows, so you do not need to use SOS for debugging unmanaged code.

Loading SOS and Running Commands

To use SOS, you must first load the SOS tool into the debugger using the Command window.

To load the SOS debugger extension

  1. First, open the dump file.
  2. From the Debug menu, choose Start and wait for execution to break.
  3. In the Command window, enter the following command:
    .load sos

Once you have loaded SOS, you can begin using the SOS commands. Each SOS command operates like a function evaluation. That means that using an SOS command blocks the Command window from receiving further input until the command finishes. If you need to, you can stop the evaluation of an SOS command using the Debug menu.

To stop an SOS command

  • From the Debug menu, choose Stop Evaluation.

SOS Command Documentation

The .NET Framework SDK Tool Developers Guide is included in version 1.1 of the .NET Framework SDK contains complete documentation on using SOS and SOS commands. You can find the Tool Developers Guide at Microsoft Visual Studio .NET 2003\SDK\v1.1\Tool Developers Guide.

See Also