Hi,
I am trying to use LLTng 2.0 (since I have no alternative for a 3.0
kernel!) and I of course use babeltrace to read them.
Problem is, I can't make any sense out of the timestamps, as I get
something like (two CPU-hog bash processes):
[1658841591493] sched_switch: { 0 }, { prev_comm =
On 12/15/2011 11:40 PM, Mathieu Desnoyers wrote:
* Gerlando Falauto (gerlando.fala...@keymile.com) wrote:
On 11/10/2011 09:06 AM, Gerlando Falauto wrote:
On 10/28/2011 09:39 AM, Mathieu Desnoyers wrote:
* Gerlando Falauto (gerlando.fala...@keymile.com) wrote:
[...]
How can I make sure that
--
Date: Thu, 15 Dec 2011 14:18:23 -0500
From: Yannick Brosseau yannick.bross...@gmail.com
The format is better, thank you. Would it be possible for you to split
the patch in several git commit and thus into several different
* Sébastien Barthélémy (barthel...@crans.org) wrote:
Hello,
I'd like to use lttng-ust 2.0 (compiled from git), but get some
trouble having it working even on
a toy project.
That is, a trace is created, but it is empty:
$ ls -nl
~/lttng-traces/auto-20111216-211946/ust/run_motion-30999
will this be in a ppa?
On 11-12-14 05:00 PM, Mathieu Desnoyers wrote:
Update: prerelease bundle 20111214 updates lttng-ust to 1.9.2 which
adds missing files to the dist tarball.
Best regards,
Mathieu
* Mathieu Desnoyers (mathieu.desnoy...@efficios.com) wrote:
LTTng, the Linux Trace
