Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] Order of trace records for input to Trace Compass

Hi David,

Events in a single trace are expected to be chronologically ordered. If they are not, you will still be able to view the trace but many things will not work properly (seeking, time synchronization, state systems, etc.).

If you keep the trace files separate, each being ordered, you can add all those traces in an experiment. Then if you open the experiment, it will automatically order all events from the contained traces chronologically.

There is also the option for you to programmatically order your trace by creating a separate sorted internal file, and use that instead of the source trace file. That is usually done by overloading the method initTrace() in your trace implementation. You have to worry about your sorting implementation not loading the whole trace in memory, if it can be very large.


On Wed, Jun 22, 2016 at 10:28 AM, David Wootton <dwootton@xxxxxxxxxx> wrote:

I have traces that I am generating a set of traces, one per process that I am converting into input to Trace Compass. If I process individual trace files sequentially, then I will be adding trace events out of timestamp order.

Will Trace Compass properly order the events or am I required to do a merge myself, ensuring events are added in the proper order?



tracecompass-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top