Open vineetsoni opened 1 year ago
No extrae.xml
file was used, but using it does not change the outcome.
Following environment variables were set before launching the trace generation:
export EXTRAE_HOME=/u/vinson3z/tools/install/extrae-4.0.1_gcc10
export EXTRAE_ON=1
export EXTRAE_COUNTERS=PAPI_L2_DCA,PAPI_L2_DCM,PAPI_L3_TCA,PAPI_L3_TCM,PAPI_TOT_CYC,PAPI_TOT_INS
export EXTRAE_INITIAL_MODE=detail
export EXTRAE_MPI_COUNTERS_ON=1
export EXTRAE_FUNCTIONS_COUNTERS_ON=1
I think the problem is coming from somewhere else. If I look at my old runs of Extrae, I had as many lines in $EXTRAE_FINAL_DIR/TRACE.mpits
as the no. of MPI processes.
However, from the recent runs, $EXTRAE_FINAL_DIR/TRACE.mpits
has only 1 line. Although there are as many .mpit
and .sym
files in the $EXTRAE_DIR
.
Bug in generating $EXTRAE_FINAL_DIR/TRACE.mpits
from $EXTRAE_DIR/*.mpit
.
mpi2prv
works if the remaining lines in $EXTRAE_FINAL_DIR/TRACE.mpits
are added manually.
Environment:
Extrae-4.0.1 built with GCC 10.2.1, Intel MPI 2021.5, PAPI 6.0.0.1 and Libunwind-1.6.2 on AlmaLinux 8.5
Execution command
mpi2prv -syn -f TRACE.mpits -e <exe> -o <output>.prv
Error log
Error backtrace (gdb)
Info
The traces are generated without any error. The exact same error is also observed using Extrae-3.8.3.
Is there any fix for this problem? Or, is it me who's using it incorrectly?