Community
Participate
Working Groups
Build Identifier: The current way of seeking will return the first event of a given timestamp. Timestamps are not necessarily always unique. This means that if you seek the second of 2 events with the same timestamp the first one will be returned. This can add extra events and skew the statistics and the state machine. Reproducible: Didn't try Steps to Reproduce: 1.Have a trace with several events with the same timestamp. (hard to make) 2.Seek in the foreground when the background request is reading between two events having the same tiemstamp.
Created attachment 185162 [details] Patch to overload the compareto event and make the sort more stable. This is a proposed fix. It overloads the compare to so that it not only checks the timestamp but also the file name. This will ensure that the order of read events will be the same. It is the first step in solving the issue if an inconsistent seek.
I believe it works in 2.0.
This bug was for Legacy LTTng which is being removed in Linux Tools 2.0.