A typical call stack is shown in Figure 1.
图1显示了一个典型的调用堆栈。
Contains the thread and method call stack frames.
包含线程和方法调用堆栈框架。
You're literally going back to a previous call stack.
也就是直接返回到一个先前的调用栈。
Display the current call stack of programs and functions.
显示程序和函数的当前调用栈。
The program "call stack" is a list of functions which led up to the current one.
程序“调用堆栈”是当前函数之前的所有已调用函数的列表(包括当前函数)。
Note, of course, that this call stack will be optimized in the ways described earlier.
注意，这个调用堆栈当然将会按前面描述的过程优化。
Instead, the programmer needs to manually list each call in the call stack of interest.
相反，程序员需要手动列出调用堆栈中的每个调用。
The cut-off percentages based on average call stack length are shown in the following table.
基于堆栈平均长度的截止百分数见下表。
The argument defines the level of the call stack for which you want to obtain the return address.
这个参数定义希望获取返回地址的调用堆栈级别。
The call stack passes the exception to the catch block, and that is how it gets returned to the user.
调用栈将异常传递给catch块，异常正是通过这种方式被返回给用户的。
Entries on the call stack can be selected, causing variables at the time of invocation to be displayed.
您可以选择调用栈中的条目，这样可以显示变量被调用时的值。
Think of the callcc as replacing the current call stack with the call stack in the continuation object.
可将callcc 视为使用continuation 对象中的调用堆栈替换当前堆栈的操作。
Note how all of the exceptions are caught, so that none of them are propagated upward to the call stack.
注意，所有这些异常是如何捕获的，因此它们不会被向上传播到调用堆栈。
To find out the call stack for the malloc call, stktrace probe function can be called in the previous script.
要想查看malloc调用的调用堆栈，可以在前面的脚本中调用stktrace探测函数。
Whenever the actual code encounters any type of error, it throws an exception, which then goes to the call stack.
每当实际代码碰到任何类型的错误，它就抛出一个异常，然后该异常就进入调用栈。
If there were many component calls before your breakpoint was hit, you would see the call stack in the Debug view.
如果在遇到断点之前有很多组件调用，将会在Debug视图中看到调用堆栈。
Note that until now I have made no mention of the origins of the thread whose call stack was depicted in Figure 1.
注意，直到现在我还没有提到图 1 中描述的调用堆栈的线程起源。
When my SCA application encounters a problem, can someone explain the various classes I see on the runtime call stack?
当我的SCA应用程序遇到问题时，如何解释运行时调用堆栈上出现的各种类？
Without a reference, you copy the entire array or hash onto the function call stack, and then copy it again in the function.
如果不使用引用，就需要将整个数组或hash 表复制到该函数的调用栈中，然后在函数中再次对其进行复制。
Because the state isn't dependent on a given call stack, the approach is more stable for things like long-duration workflows.
因为状态不依赖于给定的调用堆栈，所以这种方式对于长期工作流这样的东西更稳定。
Listing 4 shows yet another portion of the hprof output, giving call stack information for allocation sites for Map.Entry objects.
清单4展示了hprof输出的另一部分，给出了Map . Entry对象的分配点的调用堆栈信息。
The current call stack for the thread is displayed, and the current line of execution is highlighted in the editor in the Debug perspective.
该线程的当前调用堆栈就会显示出来，当前执行的代码行就会在Debug透视图中的编辑器中高亮显示。
This allowed Emacs to display more information, including the call stack, local variables of the current stack and the status of any breakpoints.
这就使得Emacs可以显示更多的信息，包括调用堆栈、当前栈的局部变量以及各断点的状态。
Rather than using programmatic transactions within the same method, you can move the update operations to another public method within the call stack.
不用在相同的方法中使用编程事务，而是将更新操作移动到调用栈的另一个公共方法中。
This object must have a method called run(), which is executed by the runtime once the current frame in the call stack is specially marked as described above.
这个对象必须有一个名为run() 的方法，在调用堆栈中的当前帧特别做了如上所述的标记时，由运行时执行这个方法。
When you put the example SCA application into a debugger and place a breakpoint on the AddService add method, you see a call stack trace similar to Listing 4.
当使用调试器调试示例SCA应用程序并在AddServiceadd方法上设置断点时，将看到如清单 4 所示的调用堆栈跟踪。
With this technique, you are effectively starting the transaction at a lower level in the call stack, thereby reducing the amount of time you are in the database.
通过此技巧，您可以有效地在调用栈的较低层次开始事务，从而减少花费在数据库中的时间。
Do you have ideas what you could do with Rubinius' transparency and accessible internals, i.e. accessing and modifying bytecode at runtime, inspecting the call stack etc.?
您是否了解应如何有效利用Rubinius清晰可见的内部结构，例如可以在运行时刻访问并修改字节码、查看调用栈？
What this rule of thumb tries to accomplish is to give a downstream component the opportunity to time out on a request before a component further up the call stack does.
这条经验规则的目标是为下游组件提供在调用堆栈的上游组件超时之前超时的机会。
Next, the ProtectionDomains on the current call stack are optimized to remove System domains as well as domains that are already present in the privileged AccessControlContext.
然后，优化当前调用堆栈上的ProtectionDomain以删除系统域以及已经出现在privileged AccessControlContext中的域。
应用推荐