Visible to Intel only — GUID: GUID-504E7E2A-B7D4-4D59-8EED-E89EB3644D88
Visible to Intel only — GUID: GUID-504E7E2A-B7D4-4D59-8EED-E89EB3644D88
Intel Inspector Filenames and Locations
User-controlled Filenames and Locations
File Type |
Default Name |
Default Location |
---|---|---|
Project (.inspxeproj) |
config.inspxeproj |
NOTE:
The filename is system controlled; however, the file location is user controlled. The default location is ~/intel/inspxe/projects/[project directory]/ |
Result (*.inspxe) produced with preset analysis type |
r@@@{at}, where:
|
~/intel/inspxe/projects/[project directory]/r@@@/ directory |
Result (*.inspxe) produced with custom analysis type |
r@@@{at}, where:
|
~/intel/inspxe/projects/[project directory]/r@@@/ directory |
Suppression (*.sup) |
default.sup |
~/intel/inspxe/projects/[project directory]/suppressions/ directory |
Result archive (*.inspxez) |
[result_name].inspxez |
~/intel/inspxe/projects/[project directory]/ directory |
Examples
If you use the default result name template and location, run a threading error analysis using a medium-scope analysis type, and then run a memory error analysis using the narrowest-scope analysis type, the Intel® Inspector names and saves the results in the following manner:
~/intel/inspxe/projects/[project directory]/r000ti2/r000ti2.inspxe
~/intel/inspxe/projects/[project directory]/r001mi1/r001mi1.inspxe
where
ti2 = threading analysis type with medium scope
mi1 = memory analysis type with narrowest scope
Other Filenames and Locations
File Type |
Filename |
File Location |
---|---|---|
Preset analysis type (.cfg) |
|
/config/analysis_type/ in the product installation directory
NOTE:
The default installation path is below /opt/intel/. For Intel® oneAPI HPC Toolkit or Intel® oneAPI IoT Toolkit installations on Linux*, the default installation path is below /opt/intel/oneapi. |
Custom analysis type (.cfg) |
[Command-line name].cfg |
~/.intel/inspxe/analysis_type/ directory |