Search Order
When locating binary/symbol/source files, the
Intel® VTune™
searches the following directories, in the following order:
Profiler
- Directory<(recursively).result dir>/all
- Additional search directories that you defined for this project in theVTuneProfilerBinary/Symbol Searchdialog box.
- For local collection, an absolute path.For remote collection, theVTunesearches its cache directory for modules copied from the remote system or tries to get the module from the remote system using the absolute path.ProfilerFor results copied from a different machine, make sure to copy all the necessary source, symbol, and binary files required for result finalization.
- For binaries, the path is captured in the result data files.
- For symbol files, the path is referenced in the binary file.
- For source files, the path is referenced in the symbol file.
On Linux*, to locate thevmlinuxfile, theVTunesearches the following directories:Profiler- /usr/lib/debug/lib/modules/`uname -r`/vmlinux
- /boot/vmlinuz-`uname -r`
- Search around the binary file.
- Search the directory of the corresponding binary file.
- On Windows*, search the directory of the corresponding binary file and alter the name of the symbol file holding the initial extension (for example,app.dll+app_x86.pdb->app.pdb).
- On Linux, search the.debugsubdirectory of the corresponding binary file directory.
- On Windows, Microsoft Visual Studio* search directories. All directories are considered as non-recursive. Directories may be specific to the selected build configuration and platform in time of collection.
- System directories.On Windows:
- Binary files:%SYSTEMROOT%\system32\drivers(non-recursively)
- Symbol files:
- All directories specified in the_NT_SYMBOL_PATHenvironment variable (non-recursively). Symbol server paths are possible here as well as in step 2.
- srv*%SYSTEMROOT%\symbols(treated as a symbol server path)
- %SYSTEMROOT%\symbols\dll(non-recursively)
On Linux:- Binary files: If the file to search is a bare name only (no full path, no extension), it is appended by the.koextension before searching in the following directories:
- /lib/modules(non-recursively)
- /lib/modules/`uname -r`/kernel(recursively)
- Symbol files:
- /usr/lib/debug(non-recursively)
- /usr/lib/debugwith appended path to the corresponding binary file (for example,/usr/lib/debug/usr/bin/ls.debug)
- Source files:
- /usr/src(non-recursively)
- /usr/src/linux-headers-`uname -r`(non-recursively)
If the
VTune
cannot find a file that is necessary for a certain operation, such as viewing source, it brings up a window enabling you to enter the location of the missing file.
Profiler
VTune
automatically applies recursive search to the
Profiler
<
directory and some system directories (Linux only). Additional directories you specify in the project configuration are searched non-recursively.
result dir
>/all- Fornon-recursive directories, theVTunesearches paths by merging the parts of the file path with the specified directory iteratively. For example, for theProfiler/aaa/bbb/ccc/filename.extfile on Linux:/specified/search/directory/aaa/bbb/ccc/filename.ext/specified/search/directory/bbb/ccc/filename.ext/specified/search/directory/ccc/filename.ext/specified/search/directory/filename.ext
- Forrecursive directories, theVTunesearches the same paths as for the non-recursive directory and, in addition, paths in all sub-directories up to the deepest available level. For example:Profiler/specified/search/directory/subdir1/filename.ext/specified/search/directory/subdir1/sub…subdir1/filename.ext.../specified/search/directory/subdir1/sub…subdirN/filename.ext.../specified/search/directory/subdirN/filename.ext
- Forsymbol server pathson Windows,symsrv.dllis used from product distributive. Customsymsrv.dll:s are not supported.