Intel® VTune™ Amplifier

Search Directories

Specify a set of search directories to locate supporting files and display analysis information in relation to your source code.

Intel® VTune™ Amplifier searches these directories when finalizing the collected data.

VTune Amplifier needs to locate the following files:

It automatically locates the files for C/C++ projects which are not moved after building the application and collecting the performance data.

In some cases, the VTune Amplifier cannot locate the supporting user files necessary for displaying analysis information and you may need to configure additional search locations or override standard ones. This is required for C++ projects with a third party library for which you wish to define binaries/sources, or for the imported projects with the data collected remotely.

To configure the search directories:

  1. Click the Configure Project toolbar button.

    The result configuration tab opens with the Analysis Target tab active.

  2. Click the Binary/Symbol Search or Source Search button on the command toolbar to open the corresponding dialog box and specify paths for symbol, binary and source files.

  3. To add a new search directory in the Search Directories table, click the <Add new search location> row and type the path and name of the directory in the activated text box, or click the browse button on the right to select a directory from the list.

    In almost all cases it is enough to configure a single search directory (top-level project directory) for all types of files. For example, if your project was initially located in /work/projects/my_project and then moved to /home/mike/my_project_copy, you need to specify the /home/mike/my_project_copy as a non-recursive search directory for all file types.

If the search directories are not configured properly, you may see the following:

If the VTune Amplifier cannot locate symbol files for system modules, it may provide incomplete stack information in the Bottom-up/Top-down Tree panes and Call Stack pane. In this case, you may see [Unknown frame(s)] hotspots when attributing system layers to user code using the Call Stack Mode option on the filter toolbar.

See Also