From d53e3a346690220e2ae206a869293f8722e347a8 Mon Sep 17 00:00:00 2001 From: Alexander Pletzer Date: Thu, 19 Mar 2026 13:20:03 +1300 Subject: [PATCH 1/2] minor edits --- docs/Software/Profiling_and_Debugging/Tracing-Tau.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/Software/Profiling_and_Debugging/Tracing-Tau.md b/docs/Software/Profiling_and_Debugging/Tracing-Tau.md index 30d05153b..3e11912a1 100644 --- a/docs/Software/Profiling_and_Debugging/Tracing-Tau.md +++ b/docs/Software/Profiling_and_Debugging/Tracing-Tau.md @@ -37,6 +37,7 @@ Confirm the versions: ```bash g++ --version mpicxx --version +cmake --version ``` ## 1. Build TAU on Mahuika @@ -75,7 +76,6 @@ Configure TAU for MPI and OpenMP (check the TAU documentation for CUDA support): -pdt=$PWD/pdtoolkit-${PDT_VERSION} \ -bfd=download -dwarf=download -unwind=download -iowrapper \ -otf=download \ - -c++=mpicxx \ -prefix=$TAU_HOME ``` Build and install TAU: @@ -89,7 +89,7 @@ Add TAU to your environment and check the `tau_exec` can be found: export PATH=$TAU_HOME/x86_64/bin:$PATH which tau_exec ``` -Verify that the Makefile has been properly installed and set the environment variable to it: +Verify that the Makefile has been properly installed and set `TAU_MAKEFILE` to it: ```bash ls $TAU_HOME/x86_64/lib/Makefile.tau-ompt-mpi-pdt-openmp export TAU_MAKEFILE=$TAU_HOME/x86_64/lib/Makefile.tau-ompt-mpi-pdt-openmp @@ -126,6 +126,8 @@ To view the traces: ```bash jumpshot upwindMpiCxx.slog2 ``` +The Java `jumpshot` application and its `jumpshot.jar` file can be copied to another platform to view the traces. For maximum interactivity, we +recommend to copy the `slog2` file to your local computer and run `jumpshot` there. !!! note "Mac Users" If you are connecting from a Mac you may need to invoke From 5e9991c27966cbef245386e4a37838cdc2236530 Mon Sep 17 00:00:00 2001 From: Alexander Pletzer Date: Thu, 23 Apr 2026 10:14:23 +1200 Subject: [PATCH 2/2] + warning banner --- docs/Software/Profiling_and_Debugging/Debugging.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/Software/Profiling_and_Debugging/Debugging.md b/docs/Software/Profiling_and_Debugging/Debugging.md index eb1d71c8b..54a3eb9ba 100644 --- a/docs/Software/Profiling_and_Debugging/Debugging.md +++ b/docs/Software/Profiling_and_Debugging/Debugging.md @@ -7,9 +7,13 @@ zendesk_article_id: 360001008136 zendesk_section_id: 360000278935 --- +!!! warning + REANNZ no longer has access to an ARM DDT parallel debugger. Discussions are under way to determine user interest in purchasing + DDT or a similar debugger. Please send an email to `support@reannz.co.nz` if you would like REANNZ to buy DDT (or another tool). + There are many reasons why a program might crash. Some Slurm job states such as `TIMEOUT` or `OUT_OF_MEMORY` can indicate a clear reason, but when -the job state is simply FAILED and the error message in the job's log +the job state is simply `FAILED` and the error message in the job's log file simply states "Segmentation Fault" or "Illegal instruction", investigations become more complicated. In the following, a selection of tools is presented which might assist. Most of the following approaches