Skip to content

how-to-examine-system-code-after-an-exception.md

Latest commit

 

History

History
40 lines (29 loc) · 1.71 KB

how-to-examine-system-code-after-an-exception.md

File metadata and controls

40 lines (29 loc) · 1.71 KB
title Examine system code after an exception
description Learn how to examine code in a system call to find the cause of the exception. The procedure applies even if symbols for the system code have not been loaded.
ms.date 11/04/2016
ms.topic how-to
dev_langs
CSharp
VB
FSharp
C++
helpviewer_keywords
debugging, exceptions
exceptions, debugging
author mikejo5000
ms.author mikejo
ms.subservice debug-diagnostics

Examine System Code After an Exception

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 Downloading 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.

Related content