Nick Curtis

Can't instrument libfabric on Crusher

10

``` $ omnitrace -v 3 -r 64 -i 1024 --min-address-range-loop 64 -o $(basename /opt/cray/libfabric/1.15.0.0/lib64/libfabric.so.1) -- /opt/cray/libfabric/1.15.0.0/lib64/libfabric.so.1 [omnitrace][exe] [omnitrace][exe] command :: '/opt/cray/libfabric/1.15.0.0/lib64/libfabric.so.1.17.0'... [omnitrace][exe] [omnitrace][exe] Option '--min-address-range-loop' specified but '--min-instructions-loop ' was...

Segfault instrumenting Cray MPI w/ v1.2.0

2

To reproduce on Crusher: ``` source sw/omnitrace-devel/share/omnitrace/setup-env.sh module load craype-accel-amd-gfx90a module load PrgEnv-cray module load rocm omnitrace -o $(basename /opt/cray/pe/lib64/libmpi_cray.so.12) -v 3 -- /opt/cray/pe/lib64/libmpi_cray.so.12 ... ``` Looking at the core...

Hang on collecting GRBM_GUI_ACTIVE in LAMMPS

3

Using: ``` OMNITRACE_CONFIG_FILE = OMNITRACE_USE_PERFETTO = true OMNITRACE_USE_TIMEMORY = false OMNITRACE_USE_SAMPLING = false OMNITRACE_USE_PROCESS_SAMPLING = false OMNITRACE_USE_ROCTRACER = true OMNITRACE_USE_ROCM_SMI = true OMNITRACE_USE_KOKKOSP = false OMNITRACE_USE_PID = true OMNITRACE_USE_RCCLP =...

Runtime instrumentation's defaults do not seem to match binary re-write's

1

Discovered when looking at PIConGPU, doing a: > omnitrace -v 3 -- ./bin/picongpu will pull in modules from libc, boost, OMPI, UCX, HIP, HSA, etc., etc. Something like 46k functions...

Segfault in dyninst when instrumenting boost

2

Due to #144, I noticed a segfault in dyninst when instrumenting boost inside in runtime instrumentation mode. This happens inside of the finalization of the dyninst instrumentation: ``` [omnitrace][exe] 769...

Same issue we saw previously in LAMMPS where dyninst isn't catching traps correctly, but now in PIConGPU. To repro use the instructions in #145 but with a binary rewrite and...

To build, follow instructions in: https://github.com/AMDResearch/omnitrace/issues/145 Use binary rewrite to instrument (no exclusions needed, as boost doesn't come in because of #144) When running, it hangs at MPI_Init with: ```...

HIP RTC example re-uses "kernel" variable

10

  I.e., if you're copy-pasting the examples, you'll get a duplicate variable name.

cdash_analyze_and_report.py: summary statistics mode

4

For my use case, I am interested in reporting summary statistics, e.g., # of passing tests, # of failed / missing tests, and a % pass rate, broken down over...