Project

General

Profile

Actions
Copy link

Bug #992

closed

Packet Context end time before start time

Added by Matthew Khouzam almost 9 years ago. Updated almost 5 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/25/2016
Due date:
% Done:

0%

Estimated time:

Description

In a 32 bit system, setting up rolling traces in UST on lttng 2.7 makes end times of packet contexts appear BEFORE the start time. This is an issue since then seeking within a trace file does not work anymore.

I have attached a sample trace to show the problem.

Babeltrace reads it fine and does not even warn about the problem.

Tracecompass fails with an error message "A trace has failed validation
Reading error: org.eclipse.tracecompass.ctf.core.CTFException: Packet begin timestamp is after end timestamp
Packet begin timestamp is after end timestamp"

Feel free to efficiosify the trace and put it in the test-spec if you want.

Files

packet-context-starttime-after-endtime.zip (1.09 KB) packet-context-starttime-after-endtime.zip Matthew Khouzam, 01/25/2016 10:55 AM
Actions
Copy link

Also available in: Atom PDF