Project

General

Profile

Bug #724

babeltrace of flight recorder trace undergoes time warp?

Added by Daniel U. Thibault about 6 years ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
Start date:
01/23/2014
Due date:
% Done:

0%

Estimated time:

Description

Assume a flight recorder trace is generated like this:

$ lttng create limkern
Session limkern created
Traces will be written in /home/daniel/lttng-traces/limkern-20140123-085831
$ lttng enable-channel channel0 -k --tracefile-size 262144 --tracefile-count 1
Kernel channel channel0 enabled for session limkern
$ lttng enable-event -k --all -c channel0
All kernel events are enabled in channel channel0
$ lttng start
(wait for a while)
$ lttng stop

Now when this is babeltraced:

$ babeltrace /home/daniel/lttng-traces/limkern-20140123-085831 -n all -f all -v -w /home/daniel/lttng-traces/limkern_nafav
[verbose] Verbose mode active
[...]
[warning] Tracer discarded 378942 events between [09:00:44.643712446] and [09:00:44.643710896] in trace UUID ce[...]22, at path: "/home/daniel/lttng-traces/limkern-20140123-085831/kernel", within stream id 0, at relative path: "channel_0_0_0". You should consider recording a new trace with larger buffers or with fewer events enabled.
[verbose] finished converting. Output written to:
/home/daniel/lttng-traces/limkern_nafav

Note how the lost events are said to lie in a nonsensical time span where the end (44.64371*0896*) is before the start (44.64371*2446*).

Using babeltrace 1.1.1-31-513413e.

Related to bug #589?


Related issues

Related to Babeltrace - Bug #589: Lost events time ranges may be offsetResolved07/09/2013Mathieu Desnoyers

Actions

Also available in: Atom PDF