To know the structure of routine calls that were made during the application execution and examine their call routes, you can profile your application with the Function Trace profiler or the Performance profiler:

Profile your application with the Function Trace or Performance profiler and get results.
In the Explorer panel, select the desired thread in the Routines category.
Select the desired routine in the Report panel.

To examine the structure of function calls, switch to the Call Tree or Call Graph panel:

The Call Tree panel displays the tree-like structure of calls for the routine that is currently selected in the Report panel. The Parents pane shows what routines called the selected routine, what routines called those routines and so on. The Children pane shows what routines were called by the selected routine, what routines were called by those routines and so on.
The Call Graph panel displays the graphical representation of the routine calls hierarchy. Each called routine is represented as a rectangle and the arrows show the sequence of routine calls.

The Performance profiler collects information on caller-callee relations and does not gather statistics on entire call routes. Results generated by this profiler provide only the general structure of function calls that are used in your application. So, in certain cases, the call Graph and Call Tree panels may display fake routes (see Tracing Call References - Specifics).

(For the Function Trace profiler only) To examine all call routes for a routine, select it in the Report panel and switch to the Details panel. The Call Route pane holds the list of call routes for the selected routine and the Call Stack panel displays the selected call stack.

Note that the Function Trace profiler can also trace and report 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.

To examine the structure of potential routine calls as they are coded in the source, use the Static Analysis profiler. See Know the Structure of Potential Routine Calls .

Know the Structure of Routine Calls in Your Application

See Also