Intel® VTune™ Amplifier 201
Intel® VTune™ Amplifier requires debug information for the binary files it analyzes to obtain accurate performance data and enable source analysis.
If your system and application modules have debug information, the VTune Amplifier is able to provide full-scale statistics on call stacks, source data, function names, and so on. For example, you may use the Call Stack Mode on the filter toolbar to select the User/system functions option and view data on both user and system functions.
If the VTune Amplifier does not find debug information for the binaries, it statically identifies function boundaries and assigns hotspot addresses to generated pseudo names func@address for such functions, for example:
If a module is not found or the name of a function cannot be resolved, the VTune Amplifier displays module identifiers within square brackets, for example: [module].
If the debug information is absent, the VTune Amplifier may not unwind the call stack and display it correctly in the Call Stack pane. Additionally in some cases, it can take significantly more time to finalize the results for modules that do not have debug information.
On Windows* operating systems, debug information is provided in PDB files. Make sure both your system and application libraries/executable have PDB files.
By default, the Microsoft Visual Studio* IDE does not generate PDB information in the Release mode. For better results with the VTune Amplifier, enable symbol generation manually.
To generate debug information for your binary files:
Right-click your C++ project and select the Properties item in the context menu.
The <your_project>Property Pages dialog box opens.
From the Configuration drop-down list, choose the Release configuration.
It may be already selected if your current configuration in the Visual Studio environment is Release.
From the left pane, select Configuration Properties > C/C++> General.
In the Debug Information Format field, choose Program Database (/Zi).
From the left pane, select Configuration Properties > Linker > Debugging.
In the Generate Debug Info field, choose Yes (/DEBUG).
Click OK to close the dialog box.
If you configured Visual Studio to generate debug information for your files, you cannot "fix" previous results because the executable and the debug information do not match the executable you used to collect the old results.
To generate a native .PDB file for a native image of .NET* managed assembly:
Use the Native Image Generator tool (Ngen.exe) from the .NET Framework. Make sure the search directories, specified in the Binary/Symbol Search dialog box, include path to the generated .pdb file.