注意，在诊断错误时，跟踪信息并不总是有用。
Note that trace information is not always helpful when diagnosing an error; for example, it might not capture the error condition if
这些跟踪信息在检测无效的格式字符串时特别有用。
This trace information is especially useful in detecting invalid format strings.
更多信息，查看解码混淆过的堆栈跟踪信息。
这样将允许基于该唯一 ID 来过滤最终的跟踪信息。
This will allow filtering of the final trace information based on that unique ID. log4j by default outputs messages that look like this
IBMJVM实现提供了许多用于生成跟踪信息的方法。
The IBM JVM implementation provides a number of ways to generate trace information.
查看跟踪信息中有关事务活动在其上发生的线程的行。
Review the lines in the trace for the thread on which the transaction activity occurs.
下面让我们看看您可以使用跟踪信息来做的一些更灵活的事情。
Let's see some more clever things you can do with your trace information. Try this command.
内联跟踪：在这种方法中，项目的更改跟踪信息在做出更改时更新。
Inline tracking: in this method change tracking information for an item is updated as the change is made.
一些用户可能想分析跟踪信息，可能对调用每个模板的频率进行计数。
Some users may want to analyze the trace information, perhaps counting how often each template was invoked.
现在，我们将通过访问异常的堆栈跟踪信息来增加一点复杂性。
Now we'll add a bit of complexity by accessing the stack trace of an exception.
终端视图中的Python堆栈跟踪信息可超链接到源代码中。
Python stack traces in the console view are hyperlinked to the source code.
她以为缺乏社会权力可能会减少人跟踪信息和制定计划以取得目标的能力。
She suspected that a lack of social power may reduce someone's ability to keep track of information and make plans to achieve his goals.
此处跟踪信息最后一行表明所超时的事务的ID为116708。
The last line of trace here shows us that the ID for the transaction that timed out was 116708.
例如，如果某个线程没有被调度，当转储缓冲区时它的跟踪信息仍然是可用的。
For example, if one particular thread is not being dispatched, its trace information is still available when the buffers are dumped or snapped.
流程所经历的路径将突出显示，并且您可以单击各个活动以查看详细的跟踪信息。
The path the process took is highlighted, and you can click on an individual activity to see the detailed trace information.
并且，如果您想记录下异常发生在何处，您不必手工分析堆栈跟踪信息。
And, if you want to log where the exception happened, you don't have to manually parse the stack trace.
您可以使用db 2 trc命令来捕捉跟踪信息，并将该信息格式化成可读的文本。
You can use the db2trc command to capture trace information and to format this information into readable text.
用于分析跟踪信息来确定事务超时的原因的方法还可以用于解决其他类型的问题。
The method used for analyzing traces to determine the cause of transaction timeouts can also be used for other types of problems.
分析事务跟踪信息时，通常有必要分析多个线程，而这将增加跟踪分析的复杂性。
When analyzing a transaction trace, it is usually necessary to follow multiple threads, which adds some complexity to the trace analysis.
我的客户机测试程序将结果打印到控制台，这样，它们就与清单6中的性能跟踪信息混在一起。
My client test program prints results to the console, so these come out intermixed with the performance trace information in Listing 6.
跟踪异常(无论它们在何处捕获)保证了有价值的堆栈跟踪信息仍然可以从生产应用程序中抽取。
Tracing exceptions wherever they are caught ensures that valuable stack trace information can still be extracted from a production application.
MaintainJ当前会在基于文件的数据库中为不同的用例分别存储运行时调用的跟踪信息。
MaintainJ currently stores the runtime call trace information for different use cases in a file system based database.
一个简单的技巧：尝试使用curl- v——trace - ascii…来生成跟踪信息。
A quick tip: Try curl -v — trace-ascii... to generate tracing information.
truss生成跟踪信息，包括进程执行的系统调用、它收到的信号和它导致的机器错误。
The command truss produces a trace of the system calls it performs, the signals it receives, and the machine faults it incurs.
但是我必须承认他的做法是值得商榷的，特别是如果您只希望在设法调试某个问题时才添加跟踪信息。
But I have to agree with him that doing so is a hassle, especially if you want to add the trace information only when you're trying to debug a problem.
一般在分析启动性能时，我会收集所有激活包的列表以及对应于它们为何激活的堆栈跟踪信息。
Typically, when analyzing startup performance, I gather a list of all the activated bundles and stack traces for why they were activated.
清单1是单个程序产生的跟踪信息的一个例子，该程序使用简单的输出来运行，输出中使用了时间戳和消息。
Listing 1 is an example of trace information coming from a single program being run using a simple output using timestamps and messages.
这种低级别的跟踪信息对Ruby解释器的开发者，以及在一定程度上对Rails核心团队来说是有用的。
This type of low level tracing information is helpful to the developers of the Ruby interpreter and, to a certain degree, the Rails core team.
如果是将跟踪信息存储到一个文件，则转储文件的大小只受空余空间和系统所允许的最大文件大小的限制。
If you are tracing to a file, the size of the dump file is limited only by the free space and maximum allowable file size on the system.
之后我找到一个调试器，你可以在浏览器中运行它并收集跟踪信息，但对于少量日志的应用来说这太复杂了。
I later found a debugger that you run in your browser to get the traces, but it was too complicated for my small logs.
应用推荐