您要查找的是不是：
- Higher up the call stack, we handle the exception. 我们在呼叫堆叠的较高层位置处理这个例外。
- View and control script flow with the Call Stack window. 利用“调用堆栈”窗口查看和控制脚本流。
- Suppresses creation of frame pointers on the call stack. 此选项取消在调用堆栈上创建框架指针。
- In the bottom portion of the window, a call stack may appear. 在该窗口的底部,可显示一个调用堆栈。
- Will be repeated once for every level in the function call stack. 在调用函数堆栈的每级只重复一次。
- You re literally going back to a previous call stack. 也就是直接返回到一个先前的调用栈。
- Then the call stack returned would be that of the server. 那么返回的调用堆栈将是服务器的。
- Method does not propagate the calling stack. 不传播该调用堆栈。
- Verify that the breakpoint was hit, and that the call stack is accurate. 确认是否命中了断点,以及调用堆栈是否准确。
- There are a number of ways to gather information about the call stack. 有许多方法可以收集关于调用堆栈的信息。
- A simpler way is for the profiler to manage its own internal call stack. 更简单的方法是让监测器管理它自己的内部堆栈。
- It stores information about the call stack leading up to the function call. 它存储有关导致函数调用的调用堆栈的信息。
- You can then look at the call stack to see how your program got to that point. 然后可以查看调用堆栈,以了解程序是怎样到达该点的。
- Does not propagate the calling stack onto the worker thread. 不将调用堆栈传播到辅助线程上。
- The native frame immediately above the managed code may be missing from the Call Stack window. 紧邻托管代码之上的本机框架可能从“调用堆栈”窗口中消失。
- Gets a string representation of the frames on the call stack at the time the current exception was thrown. 获取当前异常发生时调用堆栈上的帧的字符串表示形式。
- In the Call Stack window, right-click the frame whose code and data that you want to view. 在“调用堆栈”窗口中,右击要查看其代码和数据的帧。
- Otherwise, the call stack information displayed by the debugger may be off by one frame. 否则,调试器可能在显示一帧调用堆栈信息后就停止显示。
- At least one of the callers higher in the call stack does not have permission to configure remoting types and channels. 调用堆栈中的较高位置上至少有一个调用方没有配置远程处理类型和信道的权限。
- The Call Stack window displays the name of each function and the programming language it is written in. “调用堆栈”窗口显示每个函数的名称和编写它所用的编程语言。
