XML Option `merge::overwrite` not honored when specifying the trace name

[valentin-seitz]

When enabling the automatic merger at the end of an execution through the XML the option to not overwrite traces seems to be ignored by current versions of Extrae when providing an explicit trace name.

The interesting part of the XML:

<merge enabled="yes" 
    synchronization="default"
    tree-fan-out="16"
    max-memory="512"
    joint-states="yes"
    keep-mpits="yes"
    translate-addresses="yes"
    sort-addresses="yes"
    translate-data-addresses="yes"
    overwrite="no"
  > $TRACE_NAME$ </merge>

When we execute this with:

rm -rf set-* TRACE.*
export EXTRAE_CONFIG_FILE=extrae.xml # This contains the snippet above
pre="<EXTRAE_DIR>/lib/libmpitrace.so"

export TRACE_NAME="sometrace"
mpicxx -o main main.c
mpirun -np 2 env LD_PRELOAD="$pre" ./main 
mpirun -np 2 env LD_PRELOAD="$pre" ./main 

is that 1 trace with the name sometrace.prv is created.

The expected behavior is that there should be sometrace.prv and the second execution should not overwrite the trace, but create sometrace.0001.prv.

Note, that this behavior seems related to #123 and therefore 20ab6fd as rolling back to e.g. extrae 4.2.3, I can observe that the overwrite=no is honored but a trace with name sometr.prv is created very similar to the issue described in #123

Attached you find a small reproducing example that should work out of the box in Marenostrum5 GPP

overwrite_not_honored.tar.gz