HP Caliper 5.3 User Guide (5900-1558, February 2011)

How Functions Are Named in Reports
HP Caliper attempts to print the most complete name possible for each function listed in reports.
The general format for function names is:
load_module_name::function_name
For example:
libdl.so.l::libdl_init threads::tu_thread_destroy
If the load module name is implicit from the context, then HP Caliper prints only the simple function
name.
Consult a linker load map and disassembly listing, or both, to determine the function.
When HP Caliper finds an unnamed stub that bridges to a function, the report shows:
{ STUB }->module::function
C++ function names are fully demangled and include full type signatures.
Unnamed Functions
In certain situations, HP Caliper cannot determine the function name. Examples are:
Static function with no debug information
Unidentified stub
Stripped executable
In these cases, HP Caliper assigns the function a name using this format:
*unnamed@0xXX(YY-ZZ)*
where
XX is some number of hexadecimal digits that are shared by the start and end addresses of
the unnamed function
YY is the remaining hexadecimal digits for the start address
ZZ is the remaining hexadecimal digits for the end address
For example, the function name *unnamed@0x400000000004c(ae0-ed0)* represents an
unnamed function starting at address 0x400000000004cae0 and ending at address
0x400000000004ced0.
Unknown Functions
When HP Caliper cannot find the name of a function (because, for example, strip(1) was used
to remove symbolic information), the report lists the name of the function as:
unknown_0xattr
where attr is the starting address of the function.
The report lists a function as unknown when HP Caliper is, for any reason, unable to resolve a
function name in a shared library through import stubs.
VSE Information Shown in Report Output
Information related to components of the HP Virtual Server Environment (VSE) that can impact
performance is shown in the report output. These components are:
HP Integrity Virtual Machines
An application's performance can be impacted if it is run on a virtual machine (that is, run
within a guest operating system) in the VM environment. For each measurement run, HP Caliper
detects and reports whether the application was run on a virtual machine or not.
How Functions Are Named in Reports 111