Paraver not displaying information in the trace correctly. #19
Description
I don't know where exactly the bug happens, but since I am using wxparaver, I will add the issue here.
If the bug can be related to the paraver kernel instead, feel free to move this issue to the corresponding repository.
I used wxparaver version 4.11.4 to reproduce the bug.
I got a trace using the Extrae Annotation API with saturates the full value range of a unsigned long long which should be an unsigned 64 bit integer on most platforms. I got this trace using a patched extrae, see bsc-performance-tools/extrae#112
Attached you find a .tar.gz containing the trace generated with saturates the value range of the Extrae API.
Opening that trace, however, reveals, that neither the value shown in the timeline:
Expected: 18446744073709551614
Got: -1
Nor the .pcf file were read in correctly by paraver
I couldn't find any documentation specifying the accepted value range of paraver, but i would expect it to be similar to the Extrae API.
One possible problem I could find is that the line using TEventValue = int64_t; seems to force a signed integer representation.