Jstack pid | core — generates a stack trace.
jstackpid |core——生成堆栈跟踪。
It displays the kernel mode stack trace of the thread.
它显示线程的内核模式栈跟踪。
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 property contains a stack trace that can be used to determine where an error occurred.
这个属性包含堆叠追踪，可以用来确定何处错误发生。
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.
详细输出还显示一些内部抛出的异常（如果发生的话），包含堆栈跟踪。
Please review the stack trace for more information about the error and where it originated in the code.
请再查看一下关于错误的堆饯追踪，并且查看一下这个错误出现在编码哪里。
Listing 4 adds logging to the third try block, logging just the method name for each part of the stack trace.
清单4向第三个try块添加了日志记录功能，只记录堆栈跟踪每部分的方法名称。
The magic keystrokes will give a stack trace of the currently running processes and all processes, respectively.
上述魔术的击键会分别给出当前运行的进程和所有进程的堆栈跟踪。
There is no need for Studio's source code to understand what's happening; the stack trace alone points to the cause.
Studio的源代码不需要去理解发生了什么；栈记录就足以指出原因。
If not, you likely get a PHP stack trace, informing you that the database connection failed or the INSERT statement did not work.
否则，您可能会得到一个php堆栈跟踪，告诉您数据库连接失败或者insert语句不工作。
To deal with this, you can generate a stack trace in the constructor of the exception object during the throw exception statement.
为了解决这一问题，可以在抛出异常语句期间，在异常对象的构造函数中生成一个堆栈跟踪。
Creating and logging the exception incurs some overhead, but the stack trace is invaluable for tracking down who caused the problem.
创建并记录异常日志会导致一些时间开销，但是堆栈跟踪可以很好地用于捕获问题原因。
If this exception isn't caught, it will immediately kill the application with an error message and stack trace dumped to the console.
如果这个异常没有被捕捉到，它将立即关闭应用程序，并将一条错误消息和栈跟踪输出到控制台。
Events received from a remote node do not include user or process information or stack trace, even if the event producer supports it.
从远程节点接收到的事件不包含用户、进程信息或栈追踪，即使事件创造器支持。
In a complex product such as Domino, a stack trace of the same type of action on two different servers can produce different results.
在诸如domino这样的复杂产品中，两台不同服务器上相同类型的动作的堆栈跟踪可以产生不同的结果。
In the Error view, the limitation arises because the detailed stack trace for the exceptions cannot be reported through this snapshot.
在Error视图中，由于例外情况具体追踪树不能通过该快照得到报告，所以限制将会上升。
The stack trace shown above describes that the problem appears to have happened when a thread running on CPU 0 ran the function __memmove.
上图显示的栈跟踪描述了当CPU0上的某个线程运行function __memmove时出现的问题。
Crashing, spitting out a "sorry, you're out of luck" message, or printing out a stack trace is not error handling. That is error reporting.
程序中断，并弹出“对不起，您运气不好”的消息或打印出堆栈跟踪，这不是错误处理，而是错误报告。
Tracing exceptions wherever they are caught ensures that valuable stack trace information can still be extracted from a production application.
跟踪异常(无论它们在何处捕获)保证了有价值的堆栈跟踪信息仍然可以从生产应用程序中抽取。
应用推荐