Project

General

Profile

Bug #259

Double event when you seek by time at 0

Added by Yannick Brosseau about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
High
Category:
-
Target version:
Start date:
06/07/2012
Due date:
% Done:

0%

Estimated time:

Description

When you seek (set_pos on a bt_iterator) at the time 0 on an iterator, you will get the first event twice, the first time with the timestamp corresponding to the creation time of the buffer and the second time with the right event timestamp.

Seekpos example:
seekpos.type = BT_SEEK_TIME;
seekpos.u.seek_time = 0

If you do a seekpos.type = BT_SEEK_BEGIN, you get the right result.

it seems that the packet start time and the first event in the trace are not at the same time (the first packet start at the buffer creation time). The this the index point to the creation time and now the first event time the trace.

#1

Updated by Yannick Brosseau about 8 years ago

  • Assignee set to Julien Desfossez
#2

Updated by Julien Desfossez about 8 years ago

  • Status changed from New to Resolved

Fixed by commit 5d2a5af291195537c5a589e388ddf2e2747fd6c5

Also available in: Atom PDF