How to: Step out of Managed Code when Native Frames are Missing from the Call Stack Window

 

For the latest documentation on Visual Studio 2017, see Visual Studio 2017 Documentation.

For the latest Visual Studio 2017 documentation, see How to: Step out of Managed Code when Native Frames are Missing from the Call Stack Window on docs.microsoft.com.

If your code has native frames that are invisible in the Call Stack window, stepping out of managed code can produce unexpected results. As a workaround, you can use a breakpoint instead of Step Out.

System_CAPS_ICON_note.jpg Note

The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose Import and Export Settings on the Tools menu. For more information, see Customizing Development Settings in Visual Studio.

To step out of managed code when native frames are missing from the call stack display

  1. In the native code, set a location breakpoint after the call to managed code.

  2. On the Debug menu, choose Continue.

    When the managed call is completed, execution will stop at the breakpoint in native code.

How to: Use the Call Stack Window

Show: