The VTuneTM Performance Analyzer requires line number information and symbol information provided in the executable in order to display the function names in sampling and call graph views. It does not support other symbol files, such as .map and .pdb.
The VTune analyzer searches for symbol information in the binary file it launches. If it cannot find this information, the VTune analyzer disassembles your code and provides static analysis of the basic blocks in your code.
The VTune analyzer for Linux* (vtl) recognizes the GNU* debug formats (STABS and DWARF 2).
The following topics provide instructions on how to generate symbol and line number information using several popular compilers:
In order to drill down to kernel sources, the kernel must be compiled with debug information.
Go to the directory containing the kernel sources and edit the kernel source's top-level Makefile.
Add the -g option to the following variables:
...
# Include the make variables (CC, etc...)
...
CFLAGS_KERNEL = -g
...
# standard CFLAGS
...
CFLAGS := ... -g ...
...
Run make clean all to create the vmlinux kernel file with debug information.
After performing a sampling session, specify that file as the one to drill down on for the hotspot view.
Generating line number and symbol information preserves any existing optimizations in the monitored application.