Exceptions append a stack trace to the log.
异常把堆栈跟踪信息追加到日志。
To obtain a stack trace, use the bt command
要获得一个堆栈跟踪信息，可以使用bt命令
Procstack prints a stack trace of the process.
procstack输出进程的堆栈跟踪。
Jstack pid | core — generates a stack trace.
jstackpid |core——生成堆栈跟踪。
You can see a stack trace in the exception object.
在这个异常对象内可以看到一个堆栈跟踪。
Programmatic access to the stack trace information.
以程序的方式访问堆栈跟踪信息。
Otherwise we simply print the exception stack trace.
否则只输出异常栈行跟踪信息。
It displays the kernel mode stack trace of the thread.
它显示线程的内核模式栈跟踪。
The code below shows a snippet of the actual stack trace.
以下代码显示了实际堆栈跟踪的代码片段。
The "heart" of an NSD file is the stack trace section.
NSD文件的核心是堆栈跟踪部分。
First of all, the exception and its stack trace must be logged.
首先，必须记录异常及其堆栈跟踪状况。
The stack trace of this plug-in's activation is shown in Figure 8.
这个插件激活的栈记录见图8。
The methods listed near the top of the stack trace are prime candidates.
在堆栈跟踪信息顶部列出的方法就是主要的候选者。
However, that interface showed me a stack trace to help debug the problem.
但是该接口给出了一个堆栈跟踪，有助于调试问题。
It's not that big of a stack trace, but it is, nonetheless, a complete one.
尽管它不是一个很长的堆栈跟踪，但它是一个完整的堆栈跟踪。
When given with no arguments, displays stack trace for the current CPU context.
如果没有提供任何参数，则显示当前 CPU 上下文的栈跟踪。
Now we'll add a bit of complexity by accessing the stack trace of an exception.
现在，我们将通过访问异常的堆栈跟踪信息来增加一点复杂性。
This response wraps the stack trace of the server-side exception into the SOAP fault detail.
这个响应把服务器端异常的堆栈跟踪包进了SOAP故障详细信息中。
You add the stack_depth: 3 parameter to limit the stack trace collected when a malloc is called.
添加stack_depth：3参数，限制调用malloc时收集的栈跟踪。
That's all well and good, but sometimes it isn't obvious looking at the resulting stack trace.
虽然那样不错，但是有时在栈记录结果中不容易看出来。
The debugger recognizes this, and it is able to provide you with a complete display for the stack trace.
调试器能够识别这个指示器，并且能够向您提供用于堆栈跟踪的完整信息。
Now let's use the Stack Trace view to determine what caused it, following the same steps as before.
现在让我们用Stack Trace视图来确定其原因，步骤同前。
These runtime exceptions display the stack trace, so that you can easily find the root cause of the error.
这些运行时异常会显示堆栈跟踪，可以帮助开发人员轻松地找到错误的根源。
Its stack trace in Figure 6 confirms why this plug-in was activated after the workbench window opened.
图6中它的栈记录确定了为什么这个插件在工作台窗口打开后被激活。
A user submits a bug report containing a stack trace from the application that is currently published.
一个用户提交了来自当前发布版本的bug报告，该报告包含了堆栈调试信息。
Adding an exception to the trace logger (Listing 3) prints the error message along with a full stack trace.
把异常添加到跟踪日志记录器(清单3)打印出错误消息和完整的堆栈跟踪。
And, if you want to log where the exception happened, you don't have to manually parse the stack trace.
并且，如果您想记录下异常发生在何处，您不必手工分析堆栈跟踪信息。
If it fails, it is denoted with a red X. Clicking the X provides stack trace information for debugging.
如果失败了，则用一个红色的x来表示。点击这个x则提供一些供调试用的线索信息。
Verbose output also shows some internally thrown exceptions (if they occur), including the stack trace.
详细输出还显示一些内部抛出的异常（如果发生的话），包含堆栈跟踪。
Listing 4 adds logging to the third try block, logging just the method name for each part of the stack trace.
清单4向第三个try块添加了日志记录功能，只记录堆栈跟踪每部分的方法名称。
应用推荐