Quantcast
Channel: C#
Viewing all articles
Browse latest Browse all 1853

About Configuring Search Directories

$
0
0

When finalizing the collected data, the Intel® VTune™ Amplifier uses a set of predefined search directories to locate supporting files and display analysis information in relation to your source code. For the VTune Amplifier integrated into the Visual Studio IDE, the search directories are defined by the Microsoft Visual Studio* C++ project properties.

VTune Amplifier needs to locate the following files:

  • binaries (executables and dynamic libraries)

  • symbols (typically .pdb files)

  • source 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. For example, if the solution is moved to another machine, or if you analyzed a precompiled executable. In these cases you may see the following:

  • In the Bottom-up or Top-down Tree pane, the module shows only one [Unknown] line instead of meaningful lines with function names.

  • When you double-click a row to view the related source code, you get a Cannot find the source file window asking you to locate the source file.

To fix this, you need to click the Project Properties button and edit the settings on the Search Directories tab.

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. To avoid this, make sure to configure the Microsoft* symbol server in the Project Properties: Search Directories tab or set the _NT_SYMBOL_PATH environment variable.

Inglese

Viewing all articles
Browse latest Browse all 1853

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>