Support Notes

X Windows: X Windows is required to run the TotalView and MemoryScape GUIs on Linux and other Unix-based systems but is not required on macOS. Systems used for remote debugging, i.e. those running only the TotalView Server, do not need X Windows installed.

OpenMP: Most compilers now support OpenMP. If your compiler supports it, and if your OpenMP code compiles successfully with a supported compiler, then your OpenMP is considered supported by TotalView.

OMPD: A compiler that supports either OpenMP 5.0 or 5.2 is required. For more information on OpenMP compilers, see OpenMP Compilers and Tools on the OpenMP website. TotalView has been tested against the following OMPD compilers:

LLVM Clang 17.0.6 and 18

LLVM Flang 17.0.1

AMD Clang and AMD Clang ROCm 6.0 (AMD Clang version 17.0.0)

HPE CC/C++ and Fortran 17 and 18

CUDA debugging:

Operating systems support: Linux x86-64, Linux PowerLE, and Linux-arm64 operating systems including NVIDIA Grace/Hopper systems. Current support is for the 9.2, and 10 - 12 tool chains.

NVIDIA GPUs support: Tesla, Fermi, Kepler, Pascal, Volta, Turing, Ampere, Hopper

Notes:

1) There is limited support for the Dynamic Parallelism feature.

2) On the NVIDIA Jetson Xavier Developer Kit, you must debug applications as root. For more information, see Debugging NVIDIA CUDA Programs.

AMD ROCm debugging:

Operating systems support: Linux x86-64. Current support is for ROCm 5.4 - 6.3.

AMD ROCm GPUs support: MI50, MI100, MI200, MI300 series GPUs

Notes:

1) TV 2024.1 (or later) is required for AMD GPU MI300 devices, which require ROCm 6.0 or later.

2) TotalView's support for AMD ROCm GPUs depends on preliminary releases of the ROCm development kit. As new ROCm releases become available, TotalView will incorporate updates, and will also continue to add new ROCm debugging capabilities to future TotalView releases.

TotalView Remote Client: The Remote Client supports debugging with TotalView on a Windows, macOS, or Linux x86 front-end system while connected to a remote back-end system. For macOS and Linux, supported front-end systems are the same as the full version of TotalView. For Windows, Windows 10 and 11 are supported.

For all systems, the front-end and back-end versions must be the same. For example, for the 2025.2 version of the TotalView Remote Client, the back-end debugger must also be version 2025.2.

No license is needed to run the TotalView Remote Client, but the TotalView debugging session launched on the remote system must be licensed.

TotalView Remote Display: Remote Display is currently bundled into all TotalView releases. Supported platforms include the following: 

Linux x86-64

Microsoft Windows

Apple macOS

No license is needed to run the Remote Display, but TotalView running on the target remote system must be licensed.

ReplayEngine for reverse debugging: Supported on Linux x86-64 operating systems. On other platforms, ReplayEngine buttons and menu selections are grayed out in the UI. For more information, see Using ReplayEngine.

Replay Engine supports the IP transport mechanism on most MPI systems. It supports communication over Infiniband using either the IBverbs or the QLogic PSM transport layers on some systems. For more information, see Using ReplayEngine with Infiniband MPIs.

LiveRecorder: Debugging LiveRecorder-generated recording files up to version 8.2 of LiveRecorder is supported on Linux x86-64 operating systems.

Python debugging: Python 2.7 and 3.5 - 3.12 debugging is supported on Linux x86-64 operating systems. For more information, see Debugging Python.

C++ STL type transformations:

TotalView C++ STL type transformations are tested with the following C++ STL library and compiler configurations:

• The GNU and LLVM C++ STL library implementations

• LLVM-based compilers (such as Clang) and GNU compilers