Intel® Advisor User Guide

ID 766448
Date 7/13/2023
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents
Give Feedback

Binary/Symbol Search and Source Search Locations

When using the Standalone GUI:

Binary/Symbol Search Locations

Intel Inspector searches binary and symbol files in default locations and in locations specified in the Binary/Symbol Search tab (if specified).

The following lists describe the order and default locations that are searched. As indicated below, some directory searches examine the specified directory and its subdirectories, while other searches do not examine its subdirectories.

The search order on Windows* OS systems is the following:

  1. Search for binary and symbol files in the directories specified in the Binary/Symbol Search tab and their subdirectories (if enabled in the tab).
  2. Search for symbol files in the directories near the related (corresponding) binary file(s) just found, such as a library:
    • Check in the directory of the corresponding binary file, using the corresponding name.
    • Check in the directory of the corresponding binary file, using a related name. For example, for app.dll where a file app_x86.pdb is present, also search for file app.pdb.
  3. For symbol files, also search using symbol server paths specified in the Binary/Symbol Search tab in the following notation: srv*C:\localsymbols*http://msdl.microsoft.com/download/symbols and/or provided in Visual Studio Tools > Options > Debugging > Symbols.

  4. Search for binary files in this standard Windows OS system directory:
    • %SYSTEMROOT%\system32\drivers (subdirectories are not searched)
  5. Search for symbol files in these standard Windows OS system directories:
    • All directories specified in the environment variable_NT_SYMBOL_PATH (subdirectories are not searched)
    • srv*%SYSTEMROOT%\symbols (symbol downstream or cache path)
    • %SYSTEMROOT%\symbols\dll (subdirectories are not searched)

The search order on Linux* OS systems is the following:

  1. Search for binary and symbol files in the directories specified in the Binary/Symbol Search tab and their subdirectories (if enabled in the tab).
  2. Search for binary files in directories from the collected result that provide an absolute path name. If the file name vmlinux is present, search these directories:
    • /usr/lib/debug/lib/modules/`uname -r`/vmlinux
    • /boot/vmlinuz-`uname -r`
  3. Search for symbol files in the directories near the related (corresponding) binary file(s) just found, such as a library:
    • Check in the directory of the corresponding binary file, using the corresponding name.
    • Check in the directory of the corresponding binary file, using a related name. For example, for app.dll where a file app_x86.pdb is present, also search for file app.pdb.
    • Search in the .debug subdirectory.
  4. Search for binary files in these standard Linux OS system directories:
    • /lib/modules (subdirectories are not searched)
    • /lib/modules/`uname -r`/kernel (subdirectories are searched)
  5. Search for symbol files in these standard Linux OS system directories:
    • usr/lib/debug(subdirectories are not searched)
    • /usr/lib/debug with appended path to the corresponding binary file, such as /usr/lib/debug/usr/bin/ls.debug

Source Search Locations

A limited set of default source locations are used in addition to the locations specified in the Source Search tab.

NOTE:

When using the Intel Advisor GUI, you must specify one or more new rows (locations) in the Source Search tab so Intel Advisor tools can find your application's annotations.

The following list describes the order and default locations that are searched. As indicated below, some directory searches examine the specified directory and its subdirectories, while other searches do not examine its subdirectories.

  1. Search for source files in the directories specified in the Source Search tab. With Intel Advisor, you can indicate whether the subdirectories of these directories should be searched.
  2. Search for source files in directories from the collected result that provide an absolute path name.
  3. When using Microsoft Visual Studio*: Search for source files in Visual Studio project directories.
  4. On Linux OS systems: Search for source files in these standard Linux locations (does not search subdirectories):
    • /usr/src
    • /usr/src/linux-headers-`uname -r`

See Also