HPC Features
Debug applications running in your HPC environments faster with TotalView, by taking advantage of its abilities to: 

• Support more than 20 different MPI implementations.
• Debug multithreaded applications with pthreads, OpenMP, and TBB.
• Easily establish interactive debugging sessions within your cluster — including through batch submission systems.
• Provide visualizations of program data and variables.
• Define how aggregate data in displayed, so you can see custom data structures in simpler forms.
• Advanced NVIDIA CUDA and OpenACC GPU debugging
• Debug ROCm / HIP applications on AMD GPUs
• Perform advanced memory debugging, including memory leaks and errors.

Reverse Debugging
Speed issue resolution in HPC code by using the reverse debugging capability in TotalView to:

• Work back from a failure, error, or crash to its root cause.
• Capture a live failing process and replay the execution history to get instant visibility into what your process did and why.
• Quickly fix race conditions, segmentation faults, stackoverflow errors, and double free errors.
• Jump to a bookmark in your program's execution history.
• Full inspection of global and local variables.
• Capture hard to reproduce test and production failures during DevOps phases with Undo's LiveRecorder Software Failure Replay platform and replay the recordings in TotalView.
• Step forward and backward by function, line, and instruction.
• Support continuous integration, collaboration, and code-learning by recording code.
• Eliminate restarting your program repeatedly with different breakpoints.
• Learn new code and deliver enhancements quicker. 

Memory Debugging
Find memory leaks and buffer overruns with TotalView's scalable memory-debugging technology:

• Easily find memory leaks and understand heap usage.
• Detect malloc/free, new/delete API misuse.
• Detect buffer overruns.
• Share memory debugging data with colleagues through data files and HTML reports.
• Compare memory results between sessions to verify elimination of leaks.
• Save time and money with low overhead technology that does not require recompilation or instrumentation.

Remote Debugging
TotalView provides several mechanisms to make it easy to debug remotely.​

​​Remote UI​: Run with the full power of the TotalView User Interface from your local laptop or workstation and securely debug on a remote cluster or workstation. 

​Remote Display Client (RDC)​​: Easily establish a remote desktop debugging session with TotalView running remotely on a cluster or workstation. Works with batch schedulers such as SLURM, PBS Pro and Load Leveler as well.​ 

Customers can request the RDC for free via the software download form.

​Reverse Connect:​ Easily submit your job into a cluster and, once run, a reverse connection is made back to a waiting TotalView allowing you to efficiently debug your code.​

Languages
You can debug applications written in one or more of the following languages, using TotalView:

• C and C++
• Fortran 
• Mixed-language applications written in Python and C/C++ 

Operating Systems
The applications you debug using TotalView can run on the following operating systems: 

• Linux including Cray Linux Environment (CLE) and PowerLE
• UNIX including AIX and Solaris
• macOS 

Processors
You can use TotalView to debug and optimize code for laptops, workstations, servers, clusters, and supercomputers with the following processors: 

• ARM (aarch64)
• Intel/AMD (x86-64, x86)
• NVIDIA GPUs on Linux x86-64, Linux ARM64, and Linux PowerLE (Power9)
• NVIDIA Jetson AGX Xavier
• OpenPOWER (ppc64le)
• Power (ppc64, ppc32)
• SPARC

APIs
Use TotalView to debug code that uses the following standardized APIs, plus many more:

• CUDA
• MPI
• OpenACC
• OpenMP
• pthreads

Support Notes
Support information here in the product distribution is a snapshot. For the latest information, see the PDF version on the TotalView documentation web site.  

X Windows: X Windows is required on all platforms to run the TotalView and MemoryScape GUIs. Systems used for remote debugging, i.e. those running only the TotalView Server, do not need X Windows installed.

OpenMP: Most languages now support OpenMP. If your language supports it, and if your OpenMP code compiles successfully with one of our supported compilers, 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
– 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.0.0

CUDA debugging:

Operating systems support: Linux x86-64, Linux PowerLE/OpenPOWER, 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, please see “Using the CUDA Debugger” in the TotalView User Guide.

AMD ROCm debugging:

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

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 2024.1 version of the TotalView Remote Client, the back-end debugger must also be version 2024.1.

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 Reverse Debugging with 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. Please see the section “Using ReplayEngine with Infiniband MPIs” in the TotalView User Guide for details.

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

Python debugging: Python 2.7 and 3.5 - 3.11 debugging is supported on Linux x86-64 operating systems. For more information, please see “Debugging Python” in the TotalView User Guide.

C++ STL type transformations:
RZVernal and Tioga systems:

Python” in the TotalView User Guide.

Note 1: The Classic TotalView UI requires X11. For important notes on installing TotalView on macOS, please see the section Mac OS Installations” in the TotalView Installation Guide. 
Note 2: Support on the XK6 platform for Cray's OpenMP Accelerator Directives and Cray's OpenACC Directives. For details, see the section “Directive-Based Accelerator Programming Languages” in the TotalView User Guide.. ReplayEngine supports debugging MPI-based programs using Cray MPI over the Gemini Interconnect found on Cray XE (x86_64 only) supercomputers. 
Note 3: For details on installing and using TotalView on Cray EX (Shasta) systems, see "Running TotalView on a Cray EX (Shasta) system" in the Known Issues section of the TotalView release notes. 
Note 4: Classic TotalView UI only 
Note 5: The TotalView Message Queue Display (MQD) feature with applications using IBM MPI Parallel Environment (PE) requires the threaded version of the MPI library.