Skip to content

Tau2 #1197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CallumWalley merged 2 commits into from
Mar 23, 2026
Merged

Tau2 #1197

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d53e3a3
minor edits
pletzer Mar 19, 2026
e5d163a
Merge branch 'main' of github.com:nesi/support-docs
pletzer Mar 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/Software/Profiling_and_Debugging/Tracing-Tau.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ Confirm the versions:
```bash
g++ --version
mpicxx --version
cmake --version
```

## 1. Build TAU on Mahuika
Expand Down Expand Up @@ -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:
Expand All @@ -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
Expand Down Expand Up @@ -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.
Comment on lines +129 to +130
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

Shiver me timbers! This line be longer than a kraken's tentacle, and ye've used plain quotes where backticks be the treasure marks for commands and files. A good pirate keeps their logs readable. Wrap yer commands and filenames in backticks ( ) to make 'em stand out, savvy?

Suggested change
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.
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.
References
  1. The style guide states that inline code should be used for any text that you want the user to copy exactly, and it should be enclosed in backticks. The current change uses single quotes instead. (link)


!!! note "Mac Users"
If you are connecting from a Mac you may need to invoke
Expand Down
Loading