LTTng » Babeltrace

Stable 1.5.

This was introduced by:

commit 1c822dfb58d831ad298b704ecaea181c16d16f3f
Author: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Date:   Wed Oct 12 06:43:48 2016 -0400

    Backport the CTF-IR interface

The introducing change from master is:

Author: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Date:   Tue Feb 9 13:27:24 2016 -0500

    Handle negative time and offset from Epoch

    Handle cases where a trace have a negative offset from Epoch.
    If Epoch is arbitrary (e.g. embedded system starting at 0, without any
    network access), the "0" can be used as correlation point between
    various components, and some components could start before the
    correlation point. Therefore, especially in traces where the time is
    meant to be shown in nanoseconds or cycles from the correlation point,
    it also makes sense to have a negative time value.

    It introduces API-breaking changes in the C and Python APIs, since we
    need to be able to return negative time values, which were previously
    used as errors (-1ULL).

    The --offset and --offset-ns command line parameters can now take
    negative offset (seconds and nanoseconds) values too.

    The [sec.ns] format is used as fallback so we don't attempt to pass
    a negative time value to POSIX time-formatting APIs.

    This also fixes an inaccurate return value in an error path of
    bt_ctf_event_populate_event_header().

    Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>