This PR introduces a possible fix for the issue described in #110
I also included a small test to test the generation of the correct .pcf file.
I already discovered, that paraver seems to also has some problems reading the .pcf file correctly, as well as displaying the trace correctly. I just opened the corresponding issue in the paraver repository: https://github.com/bsc-performance-tools/wxparaver/issues/19
This PR introduces a possible fix for the issue described in #110
I also included a small test to test the generation of the correct
.pcf
file.I already discovered, that paraver seems to also has some problems reading the
.pcf
file correctly, as well as displaying the trace correctly. I just opened the corresponding issue in the paraver repository: https://github.com/bsc-performance-tools/wxparaver/issues/19