From: jerome.stadelmann@heig-vd.ch (Stadelmann Jérôme)
Subject: [ltt-dev] LTTng traces
Date: Fri, 23 Jan 2009 07:27:25 +0100 [thread overview]
Message-ID: <200901230727.26114.jerome.stadelmann@heig-vd.ch> (raw)
In-Reply-To: <20090122200749.GB11038@Krystal>
Le jeudi 22 janvier 2009 21:07:49 Mathieu Desnoyers, vous avez ?crit :
> * Stadelmann J?r?me (jerome.stadelmann at heig-vd.ch) wrote:
> > Hi all,
> >
> > I'm trying to parse and decode the trace files but it is not so easy.
> > Is there a place or a file where I could find a description of all the facilities and the events id's ?
> >
>
> In the current LTTng, there is no such thing as "facility" anymore.
> Which LTTng version are you working with ?
>
> Mathieu
I'm using the version 0.82. I've understood the trace/subbuffer header and I wish to go further in the trace files.
J?r?me
next prev parent reply other threads:[~2009-01-23 6:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 16:44 Stadelmann Jérôme
2009-01-22 20:07 ` Mathieu Desnoyers
2009-01-23 6:27 ` Stadelmann Jérôme [this message]
2009-01-29 7:29 ` Jérôme Stadelmann
2009-01-29 15:06 ` Mathieu Desnoyers
2009-02-10 12:04 ` Jérôme Stadelmann
2009-02-10 17:29 ` Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200901230727.26114.jerome.stadelmann@heig-vd.ch \
--to=jerome.stadelmann@heig-vd.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox