From: Jonas.Fornander@enea.com (Jonas Fornander)
Subject: [ltt-dev] Specification on binary and text log output?
Date: Thu, 19 Mar 2009 09:44:35 +0100 [thread overview]
Message-ID: <DC6F86A94046A64094043D44A3A708F703BF4385@sestoex02.enea.se> (raw)
Hi,
Is there a specification on both the binary format, and the text output
from LTTng?
Furthermore, is there any document or other kind of information about this
format, apart from the logs itself.
Is it possible to create just one binary log?
I'm investigating creating a log parser for our own tool chain.
Thanks,
Jonas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090319/8ea1098c/attachment-0002.htm>
WARNING: multiple messages have this Message-ID
From: Jonas.Fornander@enea.com (Jonas Fornander)
Subject: [ltt-dev] Specification on binary and text log output?
Date: Thu, 19 Mar 2009 09:44:35 +0100 [thread overview]
Message-ID: <DC6F86A94046A64094043D44A3A708F703BF4385@sestoex02.enea.se> (raw)
Message-ID: <20090319084435.GLRQlRLO-P08BBbKSI25a7E_JyYCGRzEUJ30mu0daD4@z> (raw)
Hi,
Is there a specification on both the binary format, and the text output
from LTTng?
Furthermore, is there any document or other kind of information about this
format, apart from the logs itself.
Is it possible to create just one binary log?
I'm investigating creating a log parser for our own tool chain.
Thanks,
Jonas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20090319/8ea1098c/attachment.htm>
WARNING: multiple messages have this Message-ID
From: Jonas.Fornander@enea.com (Jonas Fornander)
Subject: [ltt-dev] Specification on binary and text log output?
Date: Thu, 19 Mar 2009 09:44:35 +0100 [thread overview]
Message-ID: <DC6F86A94046A64094043D44A3A708F703BF4385@sestoex02.enea.se> (raw)
Message-ID: <20090319084435.F2BWOLdMF4ux0g5GTxLzksoisSTwrcJ42HZXDJolDeg@z> (raw)
Hi,
Is there a specification on both the binary format, and the text output
from LTTng?
Furthermore, is there any document or other kind of information about this
format, apart from the logs itself.
Is it possible to create just one binary log?
I'm investigating creating a log parser for our own tool chain.
Thanks,
Jonas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090319/8ea1098c/attachment-0001.htm>
next reply other threads:[~2009-03-19 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 8:44 Jonas Fornander [this message]
2009-03-19 8:44 ` Jonas Fornander
2009-03-19 8:44 ` Jonas Fornander
2009-03-19 19:15 ` 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=DC6F86A94046A64094043D44A3A708F703BF4385@sestoex02.enea.se \
--to=jonas.fornander@enea.com \
/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