From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] Specification on binary and text log output?
Date: Thu, 19 Mar 2009 15:15:35 -0400 [thread overview]
Message-ID: <20090319191535.GA31236@Krystal> (raw)
In-Reply-To: <DC6F86A94046A64094043D44A3A708F703BF4385@sestoex02.enea.se>
* Jonas Fornander (Jonas.Fornander at enea.com) wrote:
> Hi,
>
> Is there a specification on both the binary format, and the text output
> from LTTng?
There has been one on the binary format, but I doubt it is up-to-date.
The closest thing we currently have to a specification is a reference
implementation (lttng and lttv libltttraceread).
There has never been any specification for the text output. Note that if
you plan to parse the textDump output, you might want to try
lttv -m textDump --path_output -t tracepath
> Furthermore, is there any document or other kind of information about this
> format, apart from the logs itself.
>
Old format documentation here :
http://ltt.polymtl.ca/svn/trunk/lttv/doc/developer/format.html
(outdated)
> Is it possible to create just one binary log?
>
Not with the current lttng design. One binary log would cause too much
cache line bouncing on SMP systems anyway.
> I'm investigating creating a log parser for our own tool chain.
>
You might want to investigate using the LGPL libltttraceread library,
part of LTTV, to save yourself some time. :)
Mathieu
> Thanks,
> Jonas
> _______________________________________________
> 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
prev parent reply other threads:[~2009-03-19 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 8:44 Jonas Fornander
2009-03-19 8:44 ` Jonas Fornander
2009-03-19 8:44 ` Jonas Fornander
2009-03-19 19:15 ` Mathieu Desnoyers [this message]
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=20090319191535.GA31236@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