Hi Divya,
Make sure the text you pipe to babeltrace-log contains new lines since
these are used to split the incoming text into multiple events.
If you really want to convert a log file which really contains lines
32kb, I'd recommend using the CTF Writer C API or its Python version
(look for
The liblttng-ust-agent JAR need versioning. The manifest file contains the
appropriate information about the JAR, such as the current version.
A symlink is also created and installed in order to point to the latest
version of the JAR.
e.g: liblttng-ust-agent.jar - liblttng-ust-agent-1.0.0.jar
Merged, thanks!
Mathieu
- Original Message -
From: Christian Babeux christian.bab...@efficios.com
To: lttng-dev@lists.lttng.org
Cc: mathieu desnoyers mathieu.desnoy...@efficios.com, Christian Babeux
christian.bab...@efficios.com
Sent: Monday, November 3, 2014 3:12:26 PM
Subject:
Hi Alexander,
Just to make sure I understand the problem, is your point that lttng
add-context should not fail when multiple contexts are added just
because one of them was already present? If not, could you provide a
log demonstrating the issue?
Thanks!
Jérémie
On Sat, Nov 1, 2014 at 7:14 PM,
Hi Jérémie,
lttng add-context should not fail when several unique performance
counters added after start program with tracepoints. Now lttng add-context
fail when several unique perf_tread context added after start program with
tracepoints.
I wrote about this problem:
-- Forwarded
