ProfilerThreadDump
(Difference between revisions)
m |
m |
||
| Line 2: | Line 2: | ||
This page describes getting a threads dump from the profiled application. | This page describes getting a threads dump from the profiled application. | ||
| - | The thread dump can be taken whenever the profiler is connected to a process, no matter what the current profiling mode is. However, to take a thread dump with minimal overhead on the profiled application, start a Telemetry profiling session - see [[ProfilerTelemetry|Profiling Telemetry]]. | + | The thread dump can be taken whenever the profiler is connected to a process, no matter what the current profiling mode is. However, to take a thread dump with minimal overhead on the profiled application, start a '''Telemetry''' profiling session - see [[ProfilerTelemetry|Profiling Telemetry]]. |
Once the profiling session runs, the threads dump can be taken by clicking the '''Thread dump''' action in '''Process section''' of the Profiler window toolbar. | Once the profiling session runs, the threads dump can be taken by clicking the '''Thread dump''' action in '''Process section''' of the Profiler window toolbar. | ||
Revision as of 15:17, 9 October 2015
Getting Thread Dump
This page describes getting a threads dump from the profiled application.
The thread dump can be taken whenever the profiler is connected to a process, no matter what the current profiling mode is. However, to take a thread dump with minimal overhead on the profiled application, start a Telemetry profiling session - see Profiling Telemetry.
Once the profiling session runs, the threads dump can be taken by clicking the Thread dump action in Process section of the Profiler window toolbar.
