Fix: use path to kernel trace to look up tracer version
authorAntoine Busque <abusque@efficios.com>
Mon, 14 Dec 2015 15:53:39 +0000 (10:53 -0500)
committerAntoine Busque <abusque@efficios.com>
Mon, 14 Dec 2015 15:53:39 +0000 (10:53 -0500)
commit4ac5e2401858de26eecfd1cfd2e3db4d28e7e581
tree58663191be1eb665e2740eddf90e00373f513e1d
parent0716cff389dcc348e5045e0d71460f6667656284
Fix: use path to kernel trace to look up tracer version

Currently, only the lttng-modules version is of use for the
analyses. However, multi-domain traces, combining UST and modules,
could lead to unpredictable results wherein the tracer_version was
erroneously identified as that of the userspace tracer, which was
problematic when its version differed from that of the kernel tracer.

Extracting the version directly from the kernel trace's metadata
corrects this issue.

Signed-off-by: Antoine Busque <abusque@efficios.com>
lttnganalyses/cli/command.py
This page took 0.024625 seconds and 5 git commands to generate.