Resolving Symbol References after Data Collection

In order to provide accurate and useful information, the VTune Amplifier XE requires symbol information for the binary files it analyzes.  If it does not find debug information in the binaries, the VTune Amplifier XE displays module identifiers within square brackets, e.g., [vmlinux], in the Bottom-up/Top-down Tree panes and Call Stack pane and may not unwind the call stack correctly for the user-mode sampling and tracing analysis types.

If you've already collected data and want to provide the VTune Amplifier XE with symbol information so that it can correctly resolve addresses and call stacks, follow these steps:

  1. Open the Project Properties for the project with the data you have already collected.
  2. Click on the Search Directories tab.
  3. Add directory paths to the symbol information.  For Windows*, this means specifying the location of the PDB files.  Normally, this is not required, since the binaries contain information about where the symbol files are located, but if you have moved them or generated the PDB files on a different system, you may need to specify their location in the Search Directories.  For example, if you copy the executables from a build system for testing on your system, you should copy the PDBs and specify their location via the Search Directories.
    For Linux*, the symbol information is normally contained in the binary, but options such as gnu_debuglink will put the symbol information in separate files, in which case you will need to specify their location.
    Note: for Windows or Linux, if the symbol files are located in the same directory as the binary files, no search directory needs to be specified.
  4. After adding all necessary or desired paths, press OK
  5. Now click on the Analysis Type tab of the results and press the Re-resolve button.
The same Project Properties are available in the Visual Studio integrated Amplifier XE, as well, but it is accessed via the Project menu:
Para obter mais informações sobre otimizações de compiladores, consulte Aviso sobre otimizações.