If the Objects category is selected in the Explorer panel, the Report panel contains results for each interface object that existed when the results were being generated. This panel contains three panes: Creation Call Stack, References and AddRef/Release Call Stack. The latter two display linked data and by default are shown in a single layout.
The following sections describe information displayed in these panes:
Creation Call StackCreation Call Stack
The Creation Call Stack pane displays the routine calls that led to the creation of the object instance selected in the Report panel. The routine that created the given instance is shown at the top of the call stack.
| Note: | If the call stack is empty, most likely, you have not added any elements to the Collect Stack Information pane or you have not selected any stack area in this pane. For more information, see Specifying Modules to Be Included Into the Call Stack.
Another possible reason is the absence of debug information for profiled modules that have been added to the Collect Stack Information pane. For more information, see How AQTime Profilers Use Metadata and Debug Information. |
The pane has the following columns:
| Columns (in alphabetical order) | Description |
|---|---|
| Class Name | The name of the object class containing the routine. |
| Module Name | The name of the module containing the routine. |
| Routine Name | The name of the routine. |
| Source File | The name of the source file for the routine. The values for this column are read from the application’s debug info. If the debug info does not contain information on the file name, the column is empty. |
| Source Line | If the stack information is collected by routines during profiling (that is, if the Routines only option corresponding to the desired stack area is selected), the column specifies the number of the source code line where the routine’s implementation begins.
If the Collect info about lines option that corresponds to the desired stack area is selected, the column specifies the number of the source code line where the method that creates or deletes an object reference was called. The values for this column are read from the application’s debug info. If the debug info does not contain information on the file name, the column is empty. |
| Unit Name | The name of the unit containing the routine. |
References
The References pane lists the methods that increased (AddRef) or decreased (Release) the reference counter of the object selected in the Report panel. The pane has the following columns:
| Columns (in alphabetical order) | Description |
|---|---|
| # | The order number of method’s call. |
| AddRef/Release | The name of the method that changed the counter. Only two values are possible: either AddRef or Release. |
AddRef/Release Call Stack
The sequence of routines that caused a certain method call is shown in the AddRef / Release Call Stack pane. The AddRef / Release Call Stack pane has the following columns:
| Columns (in alphabetical order) | Description |
|---|---|
| Call No | The caller rank in the call stack. The topmost caller has an index of 0. |
| Module Name | The name of the module containing the routine. |
| Routine Name | The name of the routine. |
| Source File | The name of the source file for the routine. The values for this column are read from the application’s debug info. If the debug info does not contain information on the file name, the column is empty. |
| Source Line | If the stack information is collected by routines during profiling (that is, if the Routines only option corresponding to the desired stack area is selected), the column specifies the number of the source code line where the routine’s implementation begins.
If the Collect info about lines option that corresponds to the desired stack area is selected, the column specifies the number of the source code line where the method that creates or deletes an object reference was called. The values for this column are read from the application’s debug info. If the debug info does not contain information on the file name, the column is empty. |
| Note: | If the call stack is empty, most likely, you have not added any elements to the Collect Stack Information pane or you have not selected any stack area in this pane. For more information, see Specifying Modules to Be Included Into the Call Stack.
Another possible reason is the absence of debug information for profiled modules that have been added to the Collect Stack Information pane. For more information, see How AQTime Profilers Use Metadata and Debug Information. |
You can double-click any routine in the Creation Call Stack pane or in the AddRef / Release Call Stack table to open (if the source file is available) the corresponding code line in the Editor panel.