Mixed Code and Missing Information in the Call Stack Window
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic applies") |
|
|
|
Standard |
|
|
|
|
Pro and Team |
|
|
|
|
Table legend:
|
Applies |
.gif "Topic does not apply") |
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
Because of differences between call stacks for managed and native code, the debugger cannot always show the complete call stack when the code types mix. When native code calls managed code, you may notice the following discrepancies in the Call Stack window:
The native frame immediately above the managed code may be missing from the Call Stack window. For more information, see How to: Step out of Managed Code when Native Frames are Missing from the Call Stack Window.
For mixed-mode applications launched outside the debugger, the Call Stack window may display only the managed code and none of the native frames will be visible.
Both cases are fairly rare. In most native calls to managed code, call stacks appear correctly.