search

bsc-performance-tools / wxparaver

wxParaver is a trace-based visualization and analysis tool designed to study quantitative detailed metrics and obtain qualitative knowledge of the performance of applications, libraries, processors and whole architectures.
http://tools.bsc.es/paraver
GNU Lesser General Public License v2.1
26 stars 3 forks source link

Paraver not displaying information in the trace correctly. #19

Open valentin-seitz opened 2 months ago

valentin-seitz commented 2 months ago

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 https://github.com/bsc-performance-tools/extrae/pull/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 image

Nor the .pcf file were read in correctly by paraver image

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.

test_trace.tar.gz