Intel® Advisor

Recent Advisor problems may be caused by PIN

Lately, we have been getting many reports of problems with the analysis tools (Inspector, Advisor, and VTune Amplifier) caused by a problem with PIN, the tool they use to instrument software.

PIN problems can produce several types of error. One of the more common ones is
__bionic_open_tzdata_path: PIN_CRT_TZDATA not set!

If you believe you may be affected, please see this article for more information.

Join the Intel® Parallel Studio XE 2018 Beta program

 

We would like to invite you to participate in the Intel® Parallel Studio XE 2018 Beta program. In this beta test, you will gain early access to new features and analysis techniques. Try them out, tell us what you love and what to improve, so we can make our products better for you. 

Registration is easy. Complete the pre-beta survey, register, and download the beta software:

Intel® Parallel Studio XE 2018 Pre-Beta survey

Intel Advisor

Hi,

This is my first post so I'll try to do my best to make the issue as clear as possible. I'm trying to use Intel Advisor 2017 for the first time to verify a quite simple Fortran code and I cannot get it to work. I follow the steps included in this tutorial https://software.intel.com/en-us/get-started-with-advisor-threading-advisor, and run the GUI using these lines of code:

cd /opt/intel

source advisor_2017/advixe-vars.sh

PIN Errors in 2017 Update 3 and 4 Analysis Tools

Problem:

As of July 28th, 2017, we have been receiving many reports of people who have been having problems with the analysis tools (Intel® VTune™ Amplifier, Advisor, and Inspector) as a result of a problem with PIN, the tool they use to instrument software.

PIN problems can produce several types of error. One of the more common ones is

  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 10
  • Microsoft Windows* 8.x
  • Intel® Parallel Studio XE
  • Intel® Advisor
  • Intel® Inspector
  • Intel® VTune™ Amplifier
  • How to use the Intel® Advisor Python API

    Introduction

    You can now access the Intel® Advisor database using our new Python API. We have provided several reference examples on how to use this new functionality. The API provides a flexible way to report on useful program metrics (Over 500 metric elements can be displayed). This article will describe how to use this new functionality.

    Getting started

    To get started, you first need to setup the Intel Advisor environment.

    > source advixe-vars.sh

  • Intermediate
  • Intel® Parallel Studio XE
  • Intel® Advisor
  • Vectorization
  • Update linux kernel breaks advisor 17 update 4

    Hello,

    We did an update of our RHEL kernel from (RHEL 6.8) kernel 2.6.32-642.6.2.el6.x86_64 to (RHEL 6.9) 2.6.32-696.3.2.el6.x86_64.

    Using the last version of advisor update 4 

    ewart@bbpviz2 ~]$ advixe-cl  --version
    Intel(R) Advisor Command Line Tool
    Copyright (C) 2009-2017 Intel Corporation. All rights reserved.
    Intel(R) Advisor 2017 Update 4 (build 517067) Command Line Tool

     

    We get the following error message on a hello word. 

    [ewart@bbpviz036 learning_engine]$  advixe-cl -collect survey ./a.out 

    Isolating failure point

    Previously I collected data on KNL system with Advisor XE (survey).  I want to change the input data set and rerun.  I also want to collect different data.   I am running this the same way - but it now fails to run.  I get a message like hthis:  advixe: Collection stopped.
    advixe: Warning: The application returned a non-zero exit value.

    Then more error messages.   

    My run is something like this: mpirun -np 1 advixe-cl -collect survey -project-dir /<path>/RUNFILES/dirname /<path>/RUNFILES/FILES/Craft.exe  : -np 127 /path/RUNFILES/Craft.exe

     

    Intel Advisor runs very slowly

    I am running Intel Advisor 2017 in Visual Studio 2012. I've been able to work through the tutorial using the vec_samples example code.

    However, in the code that I am actually working on, the Advisor takes a really long time to process the results of a run of a simple test harness.

    This is the output from the Intel Advisor 2017 messages window:

    Subscribe to Intel® Advisor