These runtime exceptions display the stack trace, so that you can easily find the root cause of the error.
这些运行时异常会显示堆栈跟踪，可以帮助开发人员轻松地找到错误的根源。
When my SCA application encounters a problem, can someone explain the various classes I see on the runtime call stack?
当我的SCA应用程序遇到问题时，如何解释运行时调用堆栈上出现的各种类？
Such "applications" range from stack products, to simple runtime libraries used by the enterprise's applications and services.
此类“应用程序”的范围可以从堆栈产品到企业的应用程序和服务使用的小型运行时库。
The heap provides runtime memory allocation, like the stack, meant for data that must outlive the function doing the allocation, unlike the stack. Most languages provide heap management to programs.
堆支持运行时内存分配，和栈不同，大多数语言都允许程序使用堆管理内存。
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() 的方法，在调用堆栈中的当前帧特别做了如上所述的标记时，由运行时执行这个方法。
At runtime the StackPanel would then automatically arrange the Button controls in a vertical stack for us like below.
在运行时刻，StackPanel会自动在一个垂直地堆叠(stack)中排列我们的按钮(【译注：这也是为什么叫StackPanel的原因】)，如下所示？
In all fairness, the Runtime Spy adds overhead, especially if stack traces are captured, so true uninstrumented elapsed time is closer to 37 seconds overall from a warm start.
公平地讲，RuntimeSpy增加了开销，尤其是当需要捕获栈记录时，所以从半热态启动 (warm start) 时，实际上不加修正 (uninstrumented) 消耗的总的时间接近37秒。
In this case, the stack trace shows the ITextViewer class was ultimately loaded because the Runtime Spy perspective was opened, as shown at the bottom of the highlighted stack trace lines.
在这个例子中，栈记录显示，是由于RuntimeSpy透视图的打开而最终导致了itextviewer类的加载，如高亮的栈记录行底部所示。
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清晰可见的内部结构，例如可以在运行时刻访问并修改字节码、查看调用栈？
When a finalizer throws an exception that it does not handle, the runtime prints the exception stack trace to the console and then allows the finalizer thread to resume running finalizers.
当终结器引发它无法处理的异常时，运行时将把异常堆栈跟踪打印至控制台，然后允许终结器线程继续运行终结器。
Because the runtime allocates memory for an object by adding a value to a pointer, it is almost as fast as allocating memory from the stack.
由于运行时通过为指针添加值来为对象分配内存，所以这几乎和从堆栈中分配内存一样快。
Occurs when an exception is thrown in managed code, before the runtime searches the call stack for an exception handler in the application domain.
当托管代码抛出异常时发生，在运行时在调用堆栈中搜索应用程序域中的异常处理程序之前。
The heap provides runtime memory allocation, like the stack, meant for data that must outlive the function doing the allocation, unlike the stack.
堆提供运行时的内存分配，如堆栈，这意味着必须活得比做了分配的功能，不同的是堆栈的数据。
When a task throws an exception that it does not handle, the runtime prints the exception stack trace to the console and then returns the thread to the thread pool.
当某个任务引发了它无法处理的异常时，运行时将把异常堆栈跟踪打印至控制台，然后将线程返回至线程池。
The artificial stack limit is chosen by the common language runtime to ensure that enough space remains to throw an exception safely.
通用语言执行阶段会选择是选择人工堆叠限制，以确保有足够的空间能够安全地掷回例外状况。
The default behavior of the common language runtime is to commit the full thread stack when a thread is started.
公共语言运行时的默认行为是在线程启动时提交完整的线程堆栈。
The common language runtime helps protect managed code from these attacks by running a stack walk on all calls.
公共语言运行时通过在所有调用上运行堆栈审核，帮助保护托管代码免受这些攻击。
This demand causes the runtime to check the permissions of all callers in the call stack, starting with assembly E.
这个需求会使执行阶段从组件 E开始，检查呼叫堆叠中所有呼叫端的使用权限。
This demand causes the runtime to check the permissions of all callers in the call stack, starting with assembly E.
这个需求会使执行阶段从组件 E开始，检查呼叫堆叠中所有呼叫端的使用权限。
应用推荐