Get support

Contact support@allinea.com to obtain support for any Allinea products.

Our support team will work with you to ensure our software works as expected on your platform. We endeavor to respond to all queries within one business day.

Allinea DDT and Allinea MAP come in one combined bundle. Allinea Performance Reports is currently an individual installation package. The current release version is version 5.0-40932.

In some cases there may be a known issue for your system, compiler or MPI. Significant known issues and the release history are listed below.

User guide

Download the Allinea Forge user guide or the Allinea Performance Reports user guide . You can also access the user guides directly within the software. To do so, Select Help from the menu bar, or press F1, to display it. The user guide is also located in the doc subdirectory of the installation.

Known Issues

If the in-application user guide (F1 - User Guide) is invisible, please remove stale cached files by typing:

    
        rm -r ~/.local/share/data/Allinea
    

Allinea Peformance Reports:

  • With Intel MPI, starting a job with the "mpirun" may fail. In that case, please use "mpiexec" instead.
  • I/O metrics are not fully available on some systems, including Cray systems.
  • Floating licence files require the new licence server to be installed.
  • Xeon Phi systems using many MPI ranks per card should set ALLINEA_REDUCE_MEMORY_USAGE=1.
  • CUDA codes will run but do not show CUDA-specific metrics.

Allinea MAP:

  • Allinea MAP I/O metrics are not available on some systems, including Cray systems.
  • Allinea MAP floating licence files require the new licence server to be installed. Older licence server versions (e.g. from DDT 3.2.1) will not load Allinea MAP floating licences. You are recommended to update older licence server installations.
  • Thread activity is not sampled whilst a process is inside an MPI call with a duration spanning multiple samples.
  • Xeon Phi systems using many MPI ranks per card should set ALLINEA_REDUCE_MEMORY_USAGE=1.
  • CUDA codes will run but do not show CUDA-specific metrics.

MPICH 3:

  • MPICH 3.0.3 and 3.0.4 do not work with Allinea DDT or Allinea MAP due to a defect. MPICH 3.1 addressed this and is fully supported.

SGI MPT:

  • SGI MPT 2.11 is not supported. Use SGI MPT 2.10 instead. 
  • The Allinea sampler must be manually linked with your program. Automatic preloading of the sampler is not supported.

SLURM:

  • On Cray X-series systems only 'native' SLURM is suported - 'hybrid' mode is not supported.

Allinea DDT + CUDA:

  • To debug CUDA programs the version of the CUDA driver must match the version of the CUDA toolkit used to compile your program. For example if the CUDA 5.5 driver is installed then you must use the CUDA 5.5 toolkit to compile your program. You may use the DDT_FORCE_CUDA_VERSION to force DDT to use a particular version of CUDA debugger, e.g. by setting DDT_FORCE_CUDA_VERSION=55 for CUDA 5.5, but this is unlikely to work.
  • The CUDA 5 early access drivers contained known issues - please update to the most recent driver to ensure debugging is supported.
  • Cray CCE 8.1.2 OpenACC and previous releases will fail to generate local variables in accelerated regions. Please install CCE 8.1.3.

Allinea DDT + VisIt:

  • On Cray XK6 to use Allinea DDT's VisIt support you will need to link your program with ddtsim.so ( ddt/lib/libddtsim.so ) manually.
  • If you are using VisIt on Ubuntu/Debian/Mint you may need to set the environment variable LIBGL_ALWAYS_INDIRECT=1 before starting Allinea DDT, otherwise the VisIt GUI will fail to load. There have also been some problems with using the more recent Intel DRI drivers with VisIT, it may be necessary to use the libgl1-mesa-swx11 package (Debian/Ubunut/Mint) instead of libgl1-mesa-glx .

Further issues and workarounds can be found in the release notes ( doc/RELEASE-NOTES ). You should also consult the appendix of the user guide to note any platform, compiler or MPI issues that may affect your debugging.

Release History/Changes

Changes since Allinea Forge 5.0:

  • Patch release 5.0-40932: Fix detection of when sampler library has been statically linked to target executable. This fix essential for using MAP on a Cray machine.
  • 2015-02-02 Allinea Forge 5.0 released.

Changes for Allinea Forge 5.0:

  • Allinea Forge unified branding.
  • Edit and recompile from within DDT and MAP.
  • MAP profiles multiple threads and supports OpenMP regions.
  • Flat profile Function view in MAP. Time glyphs removed from Project Files view.
  • Replaced make-map-*-libraries and make-profiler-*-libraries scripts with a single make-profiler-libraries script.
  • Sparklines for OpenMP threads in DDT 'Focus on Process' mode.
  • Offline logs now include source code snippets and an optional memory leak report.
  • Multi-Dimensional Array Viewer supports staggered arrays.
  • Scalable startup for SLURM, including 'native' SLURM support for Cray X-series.
  • Window setup executable is signed.
  • 'Magnified mode' no longer used on MacOS X for retina displays.
  • CAPS HMPP support removed.

Changes since Allinea Reports 5.0:

  • 2015-02-02 Allinea Reports 5.0 released.

Changes for Allinea Reports 5.0:

  • Support for multiple threads. OpenMP section added to reports.
  • Replaced make-map-*-libraries and make-profiler-*-libraries scripts with a single make-profiler-libraries script.
  • Support for SGI MPT and SLURM.

Previous Releases

  • 2014-10-10 Allinea Tools 4.2.2 released.
  • 2014-05-12 Allinea Tools 4.2.1 released.
  • 2014-03-14 Allinea Performance Reports 4.2-PR released.
  • 2013-11-29 Allinea Tools 4.2 released.
  • 2013-07-22 Allinea Tools 4.1 released.
  • 2013-03-15 Allinea Tools 4.0 released.