When the sample application completes processing, you see all the trace stack and messages from the test client.
当样例应用程序完成处理时，您可以看到来自客户端的所有跟踪栈和消息。
To deal with this, you can generate a stack trace in the constructor of the exception object during the throw exception statement.
为了解决这一问题，可以在抛出异常语句期间，在异常对象的构造函数中生成一个堆栈跟踪。
When the server reports an unexpected exception, you can examine the classes and methods of the associated stack trace to determine which application caused, or was involved in, the exception.
当服务器报告一个意外的异常时，您可以检查关联堆栈跟踪的类和方法，来确定哪个应用程序导致了异常或者与异常有关。
The magic keystrokes will give a stack trace of the currently running processes and all processes, respectively.
上述魔术的击键会分别给出当前运行的进程和所有进程的堆栈跟踪。
The debugger recognizes this, and it is able to provide you with a complete display for the stack trace.
调试器能够识别这个指示器，并且能够向您提供用于堆栈跟踪的完整信息。
If this exception isn't caught, it will immediately kill the application with an error message and stack trace dumped to the console.
如果这个异常没有被捕捉到，它将立即关闭应用程序，并将一条错误消息和栈跟踪输出到控制台。
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.
现在，我们将通过访问异常的堆栈跟踪信息来增加一点复杂性。
These runtime exceptions display the stack trace, so that you can easily find the root cause of the error.
这些运行时异常会显示堆栈跟踪，可以帮助开发人员轻松地找到错误的根源。
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.
程序中断，并弹出“对不起，您运气不好”的消息或打印出堆栈跟踪，这不是错误处理，而是错误报告。
Very specific keywords taken from specific symptoms that you observed, such as an error message or error number, or the name of a class or method found in a stack trace, and so on.
取自所观察到的特定症状的非常特定的关键字，例如错误消息或错误编号，或者在堆栈跟踪中找到的类或方法名称，等等。
Events received from a remote node do not include user or process information or stack trace, even if the event producer supports it.
从远程节点接收到的事件不包含用户、进程信息或栈追踪，即使事件创造器支持。
Creating and logging the exception incurs some overhead, but the stack trace is invaluable for tracking down who caused the problem.
创建并记录异常日志会导致一些时间开销，但是堆栈跟踪可以很好地用于捕获问题原因。
It displays the kernel mode stack trace of the thread.
它显示线程的内核模式栈跟踪。
In the second case, the exception has been logged and the exception message and stack trace is available, but it doesn't contain the necessary information to resolve the exception's cause.
在第二种情况中，这个异常被记录下来，并且可以看到异常消息，也能够跟踪堆，但是它并不包含足够发现异常根源的必要信息。
Adding an exception to the trace logger (Listing 3) prints the error message along with a full stack trace.
把异常添加到跟踪日志记录器(清单3)打印出错误消息和完整的堆栈跟踪。
Tracing exceptions wherever they are caught ensures that valuable stack trace information can still be extracted from a production application.
跟踪异常(无论它们在何处捕获)保证了有价值的堆栈跟踪信息仍然可以从生产应用程序中抽取。
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语句不工作。
Stack back trace for the current active task as well as for all other tasks (by process ID).
对当前活动的任务和所有其它任务进行堆栈回溯跟踪(通过进程ID)。
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这样的复杂产品中，两台不同服务器上相同类型的动作的堆栈跟踪可以产生不同的结果。
Listing 4 adds logging to the third try block, logging just the method name for each part of the stack trace.
清单4向第三个try块添加了日志记录功能，只记录堆栈跟踪每部分的方法名称。
By retaining a copy of the mapping.txt file for each release build, you ensure that you can debug a problem if a user encounters a bug and submits an obfuscated stack trace.
通过保存发布构建版本的mapping .txt文件拷贝，确保当用户碰到bug，并把混淆后的堆栈调试跟踪信息提交给你时，你可以进行调试从而修复问题。
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 所示的调用堆栈跟踪。
Although the root cause of the error is reported correctly in the stack trace, it's obvious that the Facelets error reporting is an improvement.
虽然在栈跟踪中直接报告了错误的根本原因，但是显然Facelets错误报告是个进步。
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时出现的问题。
At DIAGLEVEL 3 (default), the db2diag.log captures a stack trace back, and even gives you the line number within the code where the exception is caught.
在DIAGLEVEL3(默认设置)上，db2diag . log捕获堆栈跟踪，甚至给出代码中捕获到异常处的行号。
If any errors occurred, a stack trace is displayed in the Console window and the lines within the stack trace are hyperlinks to the Python source code.
如果有错误出现，Console窗口中将显示堆栈跟踪信息，其中的每一行都可以通过超链接找到python源代码。
In the Error view, the limitation arises because the detailed stack trace for the exceptions cannot be reported through this snapshot.
在Error视图中，由于例外情况具体追踪树不能通过该快照得到报告，所以限制将会上升。
You add the stack_depth: 3 parameter to limit the stack trace collected when a malloc is called.
添加stack_depth：3参数，限制调用malloc时收集的栈跟踪。
You add the stack_depth: 3 parameter to limit the stack trace collected when a malloc is called.
添加stack_depth：3参数，限制调用malloc时收集的栈跟踪。
应用推荐