Arm Forge Release History

This page describes the changes between releases of Arm Forge.

To download and install the latest version of Arm Forge, see our downloads page and follow the installation steps given in the Arm Forge user guide.

For more compatibility information, see our Known Issues, Arm DDT supported platforms, and Arm MAP supported platforms topics.

Arm Forge

Version 18.1

Released: May 04, 2018

What's new in 18.1

Arm Forge 18.1 covers the following releases:

  • Arm Forge 18.1.1 - Released 8th March 2018
  • Arm Forge 18.1.2 - Released 29th March 2018
  • Arm Forge 18.1.3 - Released 4th May 2018

Changes in Arm DDT

Enhancements:

  • Updated our licensing model to include a new “Arm Allinea Studio” licence type.
  • Added support of numactl for Arm DDT.
  • Added a sanitizer plugin to Arm DDT, causing Arm DDT to stop the execution of a program if an address, memory or thread sanitizer error is detected.
  • Added support of CUDA 9 to Arm DDT.
  • Reduced Arm DDT memory overhead when using memory debugging.

DDT Bug fixes 18.1.1:

  • Fixed a visualization glitch in the Windows client graphical interface.
  • Fixed a bug causing Arm DDT to crash when using the commands “step”, “next” and “cont” in raw commands.
  • Fixed a bug which caused the multi-dimensional array viewer to display erroneous information.
  • Fixed a bug causing Arm DDT to hang when attaching to MPI processes on an oversubscribed AArch64 machine.
  • Fixed a bug causing Arm DDT to print incorrect values when slicing Fortran arrays.
  • Fixed a bug causing Arm DDT to display an incorrect pointer stack on AArch64.
  • Fixed a bug causing OpenMPI system threads to be detected and displayed as such in the Parallel Stack View on AArch64.
  • Fixed a visualization glitch in the user guide.

DDT Bug fixes 18.1.2:

  • Added support for printing stack traces which pass through both C and Fortran code, and contain strings as functions arguments.
  • Fixed an issue related to the loading of the user guide on Mac systems.

DDT Bug fixes 18.1.3:

  • Changed the UUID of the product to avoid Arm Forge being confused with the older named Allinea Forge on Windows.
  • Pinning to address in Fortran for a watchpoint no longer deletes the watchpoint.
  • Improved support for the display of slices of Fortran arrays.

Changes in Arm MAP

Enhancements:

  • Updated our licensing model to include a new “Arm Allinea Studio” licence type.
  • Improved Arm MAP’s error messages when a specific CPU metric is not available on the system.
  • Removed CPU and GPU metrics from profiles generated on platforms where the metrics are not supported.
  • Significantly reduced the overhead of Arm MAP when profiling executables or shared libraries that do not include .eh_frame_header sections.
  • Added support of numactl for Arm MAP.
  • Added an option to enable and disable metrics.
  • Improved the documentation related to custom metrics.
  • Added a message when a job is terminated because of the “--stop-after” option.
  • Using the “ALLINEA_NOTES” environment variable which enables users to add notes to the Arm MAP XML output files.

MAP Bug fixes 18.1.1:

  • Fixed a visualization glitch in the Windows client graphical interface.
  • Fixed a bug causing Arm MAP to report a tcmalloc error when trying to profile a dynamic executable compiled in an Intel programming environment on Cray systems.
  • Fixed a visualization glitch in the user guide.

MAP Bug fixes 18.1.2:

  • Fixed an issue related to the loading of the user guide on Mac systems.

MAP Bug fixes 18.1.3:

  • Changed the UUID of the product to avoid Arm Forge being confused with the older named Allinea Forge on Windows.

Known issues

Please refer to the Known Issues page.

Refer to the Release Note for further details.

Release Note for Release History 18.1

Copyright (c) 2002-2018 Arm Limited (or its affiliates). All rights reserved.

Arm Forge 18.1 provides a complete debugging and profiling environment for C, C++ and Fortran high performance code on Linux, to help you develop and tune your HPC applications. Arm Forge combines an industry-leading debugger, Arm DDT, and an out-of-the-box-ready profiler, Arm MAP.

Contents

This document provides information specific to the 18.1 release of Arm Forge.

  • Changes in this release:
    • New features and enhancements
    • Bug fixes
  • Known issues
  • System requirements
  • Installing, uninstalling, licensing
  • Running the tools
  • Where to find example code
  • How to access user documentation
  • How to contact support

For information about previous releases of Arm Forge, refer to the Release History.

Changes in this release

Arm DDT

New features and enhancements:

  • Updated our licensing model to include a new “Arm Allinea Studio” licence type.
  • Added support of numactl for Arm DDT.
  • Added a sanitizer plugin to Arm DDT, causing Arm DDT to stop the execution of a program if an address, memory or thread sanitizer error is detected.
  • Added support of CUDA 9 to Arm DDT.
  • Reduced Arm DDT memory overhead when using memory debugging.

Bug fixes 18.1.1:

  • Fixed a visualization glitch in the Windows client graphical interface.
  • Fixed a bug causing Arm DDT to crash when using the commands “step”, “next” and “cont” in raw commands.
  • Fixed a bug which caused the multi-dimensional array viewer to display erroneous information.
  • Fixed a bug causing Arm DDT to hang when attaching to MPI processes on an oversubscribed AArch64 machine.
  • Fixed a bug causing Arm DDT to print incorrect values when slicing Fortran arrays.
  • Fixed a bug causing Arm DDT to display an incorrect pointer stack on AArch64.
  • Fixed a bug causing OpenMPI system threads to be detected and displayed as such in the Parallel Stack View on AArch64.
  • Fixed a visualization glitch in the user guide.

Bug fixes 18.1.2:

  • Added support for printing stack traces which pass through both C and Fortran code, and contain strings as functions arguments.
  • Fixed an issue related to the loading of the user guide on Mac systems.

Bug fixes 18.1.3:

  • Changed the UUID of the product to avoid Arm Forge being confused with the older named Allinea Forge on Windows.
  • Pinning to address in Fortran for a watchpoint no longer deletes the watchpoint.
  • Improved support for the display of slices of Fortran arrays.

Arm MAP

New features and enhancements:

  • Updated our licensing model to include a new “Arm Allinea Studio” licence type.
  • Improved Arm MAP’s error messages when a specific CPU metric is not available on the system.
  • Removed CPU and GPU metrics from profiles generated on platforms where the metrics are not supported.
  • Significantly reduced the overhead of Arm MAP when profiling executables or shared libraries that do not include .eh_frame_header sections.
  • Added support of numactl for Arm MAP.
  • Added an option to enable and disable metrics.
  • Improved the documentation related to custom metrics.
  • Added a message when a job is terminated because of the “--stop-after” option.
  • Using the “ALLINEA_NOTES” environment variable which enables users to add notes to the Arm MAP XML output files.

Bug fixes 18.1.1:

  • Fixed a visualization glitch in the Windows client graphical interface.
  • Fixed a bug causing Arm MAP to report a tcmalloc error when trying to profile a dynamic executable compiled in an Intel programming environment on Cray systems.
  • Fixed a visualization glitch in the user guide.

Bug fixes 18.1.2:

  • Fixed an issue related to the loading of the user guide on Mac systems.

Bug fixes 18.1.3:

  • Changed the UUID of the product to avoid Arm Forge being confused with the older named Allinea Forge on Windows.

Known issues

Please refer to the Known Issues page.

System requirements

Please refer to the supported platforms pages for Arm DDT and Arm MAP.

Installation instructions

Run the graphical "installer" or the text-only "textinstall.sh" from the download tarball. You may choose to install just for you or for all users on your system.

If you are installing on a cluster, please make sure that it is available at the same path on every machine.

If you have a job submission system such as PBS or LoadLeveler running, please refer to the Configuration section in the Arm Forge user guide for additional setup information.

Full installation instructions are available in the Arm Forge user guide.

If you're installing the Remote Client for Windows, follow these instructions.

Uninstalling Arm Forge

To uninstall Arm Forge, remove the installation directory from your system:

rm -r <installation-dir>

Licences

If you do not have licence files for each product you will need to obtain them from Arm. Evaluation licences may be obtained from the Arm website.

Full licences may be obtained by emailing HPCToolsSales@arm.com. Licence files should be stored in a directory called licences below the installation directory. For a default (root) installation, that directory would be:

/opt/arm/forge/licences

and for a user-only installation it would be:

${HOME}/arm/forge/licences

Running DDT

If you are using a supported desktop environment (KDE or Gnome) you will find a DDT icon in your Development/Programming menu.

To run DDT from the command line, type:

{arm-forge-path}/bin/ddt

or, if {arm-forge-path}/bin is in your $PATH, just type:

ddt

You may optionally provide a program name as the first argument.

Upon startup you will be presented with the Welcome page. From here you may choose to run a program, attach to an existing program or open a core file.

To start debugging a program, choose Run.  In the Run window, set the path to your program in the Application field and click Run to start the program. Your chosen program will be run using mpirun.  If you have problems starting your program under DDT, first ensure it can run without DDT from the command line.

Running MAP

If you are using a supported desktop environment (KDE or Gnome) you will find a MAP icon in your Development/Programming menu.

To run MAP from the command line, type:

{arm-forge-path}/bin/map

or, if {arm-forge-path}/bin is in your $PATH, just type:

map

You may optionally provide a program name as the first argument.

Upon startup you will be presented with the Welcome page.  From here you may profile a program, or load a profile from a previous run.

To start profiling a program, choose "Profile".  In the Run window, set the path to your program in the Application field and click "Run" to start the program.

Your chosen program will be run using mpirun.  If you have problems starting your program under MAP, first ensure it can run without MAP from the command line.

Examples

Example code can be found in the installation directory:

<INSTALL_DIR>/examples

Copy the example code to a writeable directory and run the examples using the makefiles provided.

Documentation

The Arm Forge user guide is available in the <INSTALL_DIR>/doc directory.

See further documentation, help and tutorials.

Support

If you require support or would like to provide feedback, please contact allinea-support@arm.com or use the support request form.