您要查找的是不是：
- Show maximum call stack detail. 最大调用堆栈。
- 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. 然后可以查看调用堆栈,以了解程序是怎样到达该点的。
- Fax Call Duration Exceeded is the number of fax calls that were disconnected because they exceeded the UM maximum call length. 超出传真呼叫持续时间是由于超出UM最长呼叫时间而断开连接的传真呼叫数。
- During that time, many delegations had shown maximum flexibility to reach the point they had come to. 在这段时间里,许多代表团都表现出了最大限度的灵活性,以达成他们所期望的目标。
- Does not propagate the calling stack onto the worker thread. 不将调用堆栈传播到辅助线程上。
- 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. 由于托管代码和本机代码的调用堆栈之间存在差异,因此对于混合的代码类型,调试器不能始终显示完整的调用堆栈。
- A simple test will show if this is real gold. 简单的试验就能证明这是否是真金。
- The native frame immediately above the managed code may be missing from the Call Stack window. 紧邻托管代码之上的本机框架可能从“调用堆栈”窗口中消失。
