Intel® Advisor User Guide

ID 766448
Date 3/22/2024
Public

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

Document Table of Contents

Troubleshooting

You may encounter unexpected situations while using Intel® Advisor. This reference section describes symptoms and possible correction strategies for several such situations.

Issue

Details

Error Message: Application Sets Its Own Handler for Signal

When you run Survey or Suitability analysis, the following error message appears: Application sets its own handler for signal <conflicting_signal> that is used for internal needs of the tool. Collection cannot continue.

Error Message: Cannot Collect GPU Hardware Metrics for the Selected GPU Adapter

When you run GPU Roofline, the following error message appears: Cannot collect GPU hardware metrics for the selected GPU adapter.

Error Message: Memory Model Cache Hierarchy Incompatible

Error: Memory model cache hierarchy incompatible message appears when you run performance modeling step of the Offload Modeling perspective with analyze.py on the results collected with a previous release of the Intel® Advisor.

Error Message: No Annotations Found

No annotations detected in your project sources message appears when you open the Summary or Annotation Report after running the Suitability analysis of the Threading perspective.

Error Message: No Data Is Collected

When you open a report, the following error message appears: Error 0x40000024 (No data) – No data is collected.

Error Message: Stack Size Is Too Small

When you run a Survey or a Suitability analysis, the following error message appears: Stack size provided to sigaltstack is too small. Please increase the stack size to 64K minimum.

Error Message: Undefined Linker References to dlopen or dlsym

When linking your application program on Linux* OS, you see linker (ld) messages such as undefined reference to `dlopen' or undefined reference to `dlsym'.

Problem: Broken Call Tree

After running the Offload Modeling perspective, in the Accelerated Regions tab, you see unexpected issues with code regions displayed or measured data reported, such as incorrect number of trip counts or code region type.

Problem: Code Region is not Marked up

After running the Offload Modeling perspective, you see that a code region of interest is not analyzed and has Outside of Marked Region message in the Details pane of the Accelerated Regions tab.

Problem: Debug Information Not Available

After you run any Intel Advisor analysis, the displayed report contains information about your target's debug (symbol) information that is unexpected or does not make sense.

Problem: No Data

A No Data message appears when you open a report.

Problem: Source Not Available

After you run the Intel Advisor analysis, the displayed report may contain information about your target's source code that is unexpected or does not make sense.

Problem: Stack in the Top-Down Tree Window Is Incorrect

After you run any Intel Advisor analysis, the Top-Down view in the displayed shows application stack that is unexpected or does not make sense.

Problem: Survey Analysis does not Display Report

After you run the Survey analysis in any Intel Advisor perspective, a message appears instead of the report saying that your target runs too quickly or that the target does not contain debug symbol information.

Problem: Unexpected C/C++ Compilation Errors After Adding Annotations

After adding Intel Advisor annotations, you see unexpected compiler messages when building your C/C++ target executable.

Problem: Unexpected Unmatched Annotations in the Dependencies Report

After running Intel Advisor Dependencies analysis, you see unmatched problems reported caused by unmatched annotations execution that you did not expect.

Warning: Analysis of Debug Build

A message appears when you start the Survey or Suitability analysis and the current application is built in a Debug mode.

Warning: Analysis of Release Build

A message appears when you start the Dependencies analysis and the current application is built in a Release mode.