When the Routines Data category is active in the Explorer panel, the Report panel shows profiling results for individual routines.

The panel contains the following columns:

Columns (in alphabetical order) Description

Analysis Result

Specifies if the routine was instrumented or not. If the routine was instrumented, this column is empty. Otherwise, the column displays a short description of why the routine was not instrumented:

Less than 5 bytes - The routine occupies less than 5 bytes in memory (for 32-bit applications). See Profiling Small Functions.

Less than 6 bytes - The routine occupies less than 6 bytes in memory (for 64-bit applications). See Profiling Small Functions.

No line info - The routine was added to a line-level area, but debug information does not contain info about routine lines. These routines can be profiled only at the routine level.

Unsafe code - AQTime was not able to instrument the routine safely. This typically occurs when the routine’s binary code is intermixed with data areas. See Profiling Routines That Have Unsafe Code.

No ret instruction - The routine’s binary code does not contain the ret instruction (this may happen if the routine finishes with the jmp instruction). See Profiling Routines That Do Not Have the Ret Instruction.

Duplicated code - The routine whose code coincides with that of another routine. To learn more about this, see Profiling Duplicated Code.

Class Name If the routine is a method, this is the name of the class to which it belongs.

Code Type

Specifies the type of the routine’s code. The following values are possible:

MSIL - Managed-code routine with MSIL (Microsoft Intermediate Language) code.
x64 - 64-bit code routine.
x86 - Native-code (unmanaged) routine.
Pseudo - Pseudo routine that was created by the context. For example, <JIT Compiler>, <Garbage Collector>, <Unknown PInvoke> or <Root>.
PInvoke - Native-code routine for which there is a declaration in one of managed modules and which is called from within unmanaged code.
NGen - Managed routine that was compiled by the ngen utility (CLR Native Image Generator) with the /prof argument in its command line. The ngen compilation means that the routine was compiled before the application starts.
Script - The routine belongs to a script that was profiled along with the host application. See Profiling Scripts - Overview for details.
Byte-code - Java routine that was compiled into an intermediate byte-code format. See Profiling Java Applications for details.

Lines Covered

Specifies the number of the routine’s source lines that were executed during the profiler run.

Note:

Partially executed lines are counted as executed.

Lines Uncovered Specifies the number of the routine’s source lines that were not executed during the profiler run.

Mark

Specifies if the routine was executed or not during the profiler run.

If the routine was profiled at the routine level, Mark contains a green dot if the method was executed or a red dot if the method was not executed.

If the method was profiled at the line level, Mark contains a green dot if all lines of the method were executed, a red dot if no lines of the method were executed and a yellow dot if some lines were executed and others were not.

Method Signature

Applies to results of Java application profiling. Describes types of input parameters and the return value of a Java method. The general form of a method signature argument is: (argument-types)return-type, and it may contain signatures for the following data types:

Signature	Java Type
Z	boolean
B	byte
C	char
S	short
I	int
J	long
F	float
D	double
L fully-qualified-classname;	object of the specified class
[ type	array of the specified type

Module Name The name of the module which contains the profiled routine.

Routine Name Name of the routine.

Source File The name of the source file for the method. Values for this column are read from the application’s debug info. If debug info does not contain information on the file name, the column is empty.

Source Line The source file’s line number where the routine’s implementation begins. Values for this column are read from the application’s debug info.

Total Lines The total number of source code lines in the routine.

% Covered The percentage of covered lines against the total number of lines in the routine. Partially executed lines are counted as executed.

Light Coverage Profiler - Report Panel (Routines Data Category)

See Also