Tento prehliadač už nie je podporovaný.
Inovujte na Microsoft Edge a využívajte najnovšie funkcie, aktualizácie zabezpečenia a technickú podporu.
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.
Školenie
Modul
Review the principles of code debugging and exception handling - Training
This module examines code validation using a combination of testing, debugging, and exception handling. The debugging process and benefits provided by code debugger are reviewed, along with the principals and processes behind exception handling.
Dokumentácia
Tips and tricks in the debugger - Visual Studio (Windows)
Explore some of the lesser-known features supported by the Visual Studio debugger, such as keyboard shortcuts, data tips, and code editing during debugging.
View the call stack in the debugger - Visual Studio (Windows)
Use the Call Stack window in the Visual Studio integrated development environment (IDE) to view the function or procedure calls that are currently on the stack.
Create a visual map of the call stack - Visual Studio (Windows)
Create a code map to visually trace the call stack as you debug. Make notes on the map to track what the code is doing, so you can focus on finding bugs.