它显示线程的内核模式栈跟踪。
此位置将展开以显示线程的调用堆栈。
显示线程在更新显示之前必须等待清除互斥体。
The display thread must wait for the mutex to be clear before updating the display.
其中还包括一个进程表视图，用于在经过排序的表格中显示线程列表。
There is also a process table view, which can actually show you a list of threads in a sorted table.
输出：线程的图形视图、加载多个线程转储以显示线程历史记录的能力。
Output: Graphical view of threads, ability to load multiple thread dumps to show thread history.
如果调试器用户界面(UI)要向用户显示线程的操作系统(OS)挂起计数，便可能需要考虑此信息。
The debugger user interface (UI) may want to take this information into account if it displays the operating system (OS) suspend count of the thread to the user.
换句话说，工具提供的视图不仅仅可以显示类和类实例的交互作用，而且可以显示线程、进程和主机之间的交互作用。
In other words, the views provided by the tool are able to present not only the interactions of classes and class instances, but also interactions among threads, processes, and hosts.
调试器显示所有正在运行的线程列表，您可以在这里检查变量，这里也是可以逐步执行源代码的另一个位置。
The debugger shows a list of all the running threads, an area where you can examine variables, and another area where you can step through source code.
清单5显示如何确定是否缓存了足够的线程。
Listing 5 shows how to determine if you have enough threads cached.
清单1显示在忘记联接可接合线程时引发的严重内存泄漏。
Listing 1 shows the serious memory leak created if you forget to join joinable threads.
这些阅读器可以使用该扩展来将条目的评论显示为线程的讨论。
Those readers can use that extension to display comments to an entry as a threaded discussion.
此示例显示了维护线程如何使用获得时间和未使用超时属性防止连接过时。
This example has shown how the maintenance thread USES the Reap time and Unused timeout properties to prevent stale connections.
标签中的第一行显示，该线程需要32个字节，而且，自上次内存分配失败以来(即自上次发生gc以来)，已经有286毫秒的时间。
The first line in the tag shows that the thread needed 32 bytes and it has been 286 milliseconds since the last memory allocation failure (i.e., since the last GC occurred).
左上方的窗格显示当前正在执行的线程。
上图中第一个灰色段显示的是这些线程的对齐，它们可以使用偏向锁（注意所有地址都以00结尾）。
The first section in grey is reporting on the alignment of these thread object so that it may work with biased locking (note all addresses end with 00).
当所有的线程都在等待，该跟踪会显示哪些线程是死锁的并可能在等待相同的信号量。
When all threads are waiting, the trace shows which threads are deadlocked and possibly waiting on the same semaphore.
右击线程将会显示如图33所示的背景菜单。
Right clicking the thread will show the context menu seen in Figure 33.
图8的右边显示了拒绝理由的线程，其中三种颜色表示三种拒绝理由。
The right side of Figure 8 shows the threads of reject reasons with three colors indicating three types of reject reasons.
左列显示了所有运行线程的名称。
The left-hand column displays the names of all running threads.
JTop将显示当前应用程序内运行线程的CPU使用情况。
JTop shows the CPU usage of the threads running within the current application.
线程使用：显示代码的线程层次的行为。
Threads选项卡显示此会话中使用的线程的详细信息。
The threads TAB displays details about the threads used in this session.
Overview选项卡以图形的格式显示有关内存使用、线程、类和CPU 使用情况的信息。
The Overview tab displays correlated information about memory usage, threads, classes, and CPU usage in a graphical format.
此Portlet显示了服务器上的可用线程池以及每个池的大小(图1)。
The portlet displays the thread pools available on the server and the size of each pool (Figure 1).
如果问题是deadlock，线程分析工具将会显示哪个线程是您期望它工作，但是实际上在等待永远也不会发生的东西。
If the problem is a deadlock, thread analysis tools will show that threads that you expect to be working are actually waiting for something that is never going to happen.
还可以通过MailPreferences对话框中的新选项，在阅读邮件时，在底部面板中显示这些线程。
You can also display them while reading mail in the bottom pane through a new option in the mail Preferences dialog box.
程序中的每个线程都显示为树中的一个节点，Debug视图显示了每个运行目标的进程。
Each thread in your program appears as a node in the tree, and the Debug view displays the process for each target you're running.
这个命令将显示客户机的第24个线程产生的输出。
This shows you the output from the 24th thread of the client.
对于每一个调试下的过程，调试视图会显示所有它所运行的线程。
For each process under debug, the debug view displays all its running threads.
对于每一个调试下的过程，调试视图会显示所有它所运行的线程。
For each process under debug, the debug view displays all its running threads.
应用推荐