ctf: Ignore invalid clock description elements
authorAlexandre Montplaisir <alexmonthy@efficios.com>
Mon, 8 Feb 2016 21:45:28 +0000 (16:45 -0500)
committerMatthew Khouzam <matthew.khouzam@ericsson.com>
Wed, 10 Feb 2016 21:53:34 +0000 (16:53 -0500)
commit01b1449cf1ec14b1468f56125cf5d4ccfdcd9c06
tree972b2a8e01df8556f3380bb4577090b2cd10d2ac
parente14c1f714a84692e206d6818a4c3ca735e572e63
ctf: Ignore invalid clock description elements

The clock "offset" element is supposed to be signed integer constant[1].
LTTng uses 64-bit integers for this, however there is a bug with current
versions where this can be set to values above 2^63.

Right now Trace Compass refuses to open the trace and reports the
invalid value as a CTF error. We could accomodate and still load these
traces, ignoring the invalid definitions.

[1] This is not explicitly mentionned in the spec, but it was discuted
    with the spec's authors, and it should be updated in the future.

Change-Id: I44fc4f4b90c1c9f046c03d83d63cea2fee8bb57f
Signed-off-by: Alexandre Montplaisir <alexmonthy@efficios.com>
Reviewed-on: https://git.eclipse.org/r/66159
Reviewed-by: Hudson CI
Tested-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
ctf/org.eclipse.tracecompass.ctf.core/src/org/eclipse/tracecompass/internal/ctf/core/event/metadata/tsdl/ClockParser.java
This page took 0.024798 seconds and 5 git commands to generate.