We have generated CTF trace file with multiple streams for each core and in some cases CTF events can have same timestamp during to sampling rate faster than clock speed. In this case the order seems to be what ever created first and assigned reader.
Event in stream file 1:Â Â 001 Core 0 Started work
Event in stream file 2:Â Â 001 Core 1 Completed work
001 Core 1ÂCompletedÂwork
001 Core 0 Started work
Looks likeÂCTFTraceReader() hasÂStreamInputReaderTimestampComparator() which is a bit inflexible to extend or modify.
Any suggestions to make it shown as written. I understand no other information to order them but we can add extra attribute during creation to set the order.