图1显示了一个典型的调用堆栈。
像图1显示的这样一个调用堆栈快照将编写为(codified)为一个AccessControlContext并由AccessController对象提供的本机方法调用返回。
A call stack snapshot like the one shown in Figure 1 would be codified as an AccessControlContext and returned by native method calls provided via the AccessController object.
通过调用每个元素的不同方法，您可以用任何自己喜欢的格式来显示堆栈转储信息。
By calling the various methods of each element, you can display the stack dump in any format you'd like.
该线程的当前调用堆栈就会显示出来，当前执行的代码行就会在Debug透视图中的编辑器中高亮显示。
The current call stack for the thread is displayed, and the current line of execution is highlighted in the editor in the Debug perspective.
这就使得Emacs可以显示更多的信息，包括调用堆栈、当前栈的局部变量以及各断点的状态。
This allowed Emacs to display more information, including the call stack, local variables of the current stack and the status of any breakpoints.
有调用堆栈提供与但并不总是显示被用户的编码功能的序列。
There is call stack provided in VS but isn't always show the sequence of functions called by user's code.
使用快捷菜单可以选择显示非用户代码的调用堆栈信息。
You can choose to display the call stack information for non-user code by using the shortcut menu.
在多数对托管代码的本机调用中，都会正确显示调用堆栈。
In most native calls to managed code, call stacks appear correctly.
此位置将展开以显示线程的调用堆栈。
显示每个争用资源的阻塞事件的图形时间线，并列出阻塞事件的调用堆栈。
Displays a graphical timeline of the blocking events for each contended resource and lists the call stack for the blocking events.
由于托管代码和本机代码的调用堆栈之间存在差异，因此对于混合的代码类型，调试器不能始终显示完整的调用堆栈。
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.
由于托管代码和本机代码的调用堆栈之间存在差异，因此对于混合的代码类型，调试器不能始终显示完整的调用堆栈。
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.
应用推荐