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

This topic applies to:

Visual Studio Edition

Visual Basic

C#

C++

J#

Web Dev

Express

No

No

Yes

No

No

Standard

No

No

Yes

No

No

Pro/Team

No

No

Yes

No

No

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.

NoteNote

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 Visual Studio Settings.

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. From the Debug menu, choose Continue.

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

See Also

Tasks

How to: Use the Call Stack Window