Trace Executed Functions

Using Function Trace Profiler

Using Performance Profiler

Quick Analysis of Unmanaged Applications

To know what methods were executed during your application execution, use the Function Trace profiler:

1. Run the Function Trace profiler and get results.

2. In the Explorer panel, select the Routines category.

3. Examine the Report panel that lists all routines called during the application execution.

4. Select the desired routine in the Report panel and view the call stack for the selected routine in the Details panel.

The Function Trace profiler also traces and reports the actual sequence of function calls for a thread. To view this information, select the Call Trace category in the Explorer panel and examine the sequence of function calls and call characteristics shown in the Report and Details panels.

Another way to know what functions were executed during the application run is to use the Performance profiler:

1. Run the Performance profiler and get results.

2. If the  Show non-hit routines button is not pressed on the Profiler toolbar (default), then among all of the routines included in the profiling, the Report panel displays only those that were executed during the run (Hit Count > 0).

3. If the Show non-hit routines button is pressed, the Report panel will display all functions that were executed (that is, JIT-compiled). Note that it will even show those functions that were not included in profiling tasks. However, no information on these functions will be available in the panels.

The fastest (but the least accurate) way to know what functions were executed during the application run is to use the Sampling profiler:

1. Run the Sampling profiler and get the results.

2. In the Explorer panel, select the Routines category.

3. Examine the Report panel.

   During the profiling, the Sampling profiler takes samples at regular time intervals to determine which routines are being executed in the application. The Report panel lists routines that took at least one sample during the profiling.

4. To get more detailed and accurate information, continue analyzing the application with the Performance or Function Trace profiler as described above.

The Sampling profiler can overlook some “quick” routines that start and complete their run during the intervals between two samples. You can use the Sampling profiler to explore only unmanaged applications.