From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng traces
Date: Thu, 29 Jan 2009 10:06:26 -0500 [thread overview]
Message-ID: <20090129150625.GA7515@Krystal> (raw)
In-Reply-To: <200901290829.25380.jerome.stadelmann@heig-vd.ch>
* J?r?me Stadelmann (jerome.stadelmann at heig-vd.ch) wrote:
> Hi Mathieu,
>
> Excuse-me for asking again but, is there really no other way to go than scanning the source code in order to understand the traces format and information ?
> For your question, I'm using the version 0.82.
>
I would recommend :
starting with ltt/ltt-serialize.c : there is a very lengthy comment in
there which explains the format strings and how the generic serializer
writes the event data.
Looking at ltt/probes/ltt-type-serializer.h to see how the specialized
probes write the event information.
And for a more palatable document :
(latest publicly available version of ISO/IEC 9899:1999, Programming
Languages - C)
http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1256.pdf
Section 6.7.2.1 Structure and union specifiers
LTTng event fields follow a subset of the ISO C standard for structures.
Specific note : unlike the standard C implementations, there is no
padding at the end of the event payload (structure). Also note that
LTTng does not support bitfields in C structures because they depend on
the specific compiler implementation.
Hope this helps,
Mathieu
> Best regards,
> Jerome
>
> 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
> >
> > > Thank you
> > > Jerome
> > >
> > > _______________________________________________
> > > ltt-dev mailing list
> > > ltt-dev at lists.casi.polymtl.ca
> > > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> > >
> >
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-01-29 15:06 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
2009-01-29 7:29 ` Jérôme Stadelmann
2009-01-29 15:06 ` Mathieu Desnoyers [this message]
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=20090129150625.GA7515@Krystal \
--to=compudj@krystal.dyndns.org \
/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