Actions
Bug #9334
closedtimestamp reset at MIPS trace
Start date:
10/17/2018
Due date:
% Done:
100%
Estimated time:
Detected in build:
qemu4v.master
Platform:
Published in build:
0.2.4-beta-181112
Description
In MIPS programs related traces the following timestamp resetting events happen:
262 clk 0 IT (262) ffffffffbfc0ff30 nop 263 clk 0 IT (263) ffffffffbfc0ff34 nop 264 clk 0 IT (264) ffffffffbfc0ff38 nop 265 clk 0 IT (265) ffffffffbfc0ff3c nop 266 clk 0 IT (266) ffffffffbfc0ff40 nop 267 clk 0 IT (267) ffffffffbfc0ff44 nop 268 clk 0 IT (268) ffffffffbfc0ff48 nop 269 clk 0 IT (269) ffffffffbfc0ff4c nop 270 clk 0 IT (270) ffffffffbfc0ff50 nop 271 clk 0 IT (271) ffffffffbfc0ff54 nop 272 clk 0 IT (272) ffffffffbfc0ff58 nop 273 clk 0 IT (273) ffffffffbfc0ff5c nop 274 clk 0 IT (274) ffffffffbfc0ff60 nop 0 clk 0 IT (0) ffffffffbfc0ff64 nop 1 clk 0 IT (1) ffffffffbfc0ff68 nop 2 clk 0 IT (2) ffffffffbfc0ff6c nop 3 clk 0 IT (3) ffffffffbfc0ff70 nop 4 clk 0 IT (4) ffffffffbfc0ff74 nop 5 clk 0 IT (5) ffffffffbfc0ff78 nop 6 clk 0 IT (6) ffffffffbfc0ff7c nop 7 clk 0 IT (7) ffffffffbfc0ff80 nop 8 clk 0 IT (8) ffffffffbfc0ff84 nop 9 clk 0 IT (9) ffffffffbfc0ff88 nop
It looks like the trace contains a number of similar fragments of the same execution. The timestamp value should grow steadily, without any resets.
Actions