Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

How to: Examine System Code After an Exception

This topic applies to:

Edition

Visual Basic

C#

C++

Web Developer

Express

Topic appliesTopic appliesTopic appliesTopic does not apply

Standard

Topic appliesTopic appliesTopic appliesTopic does not apply

Pro and Team

Topic appliesTopic appliesTopic appliesTopic 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 an exception occurs, you might have to examine code inside a system call to determine the cause of the exception. The following procedure explains how to do this if you do not have symbols loaded for the system code or if Just My Code is enabled.

To examine system code following an exception

  1. In the Call Stack window, right-click, then click Show External Code.

    If Just My Code is not enabled, this option is not available on the shortcut menu and system code is shown by default.

  2. Right-click the external code frames that now appear in the Call Stack window.

  3. Point to Load Symbols From and then click Microsoft Symbol Servers.

    1. If Just My Code was enabled, a dialog box appears. It states that Just My Code has now been disabled. This is necessary for stepping into system calls.

    2. The Dowloading public symbols dialog box appears. It will disappear when downloading finishes.

  4. You can now examine the system code in the Call Stack window and other windows. For example, you can double-click a call stack frame to view the code in a source or Disassembly window.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft