From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Need help in converting trace data into CTF
Date: Wed, 29 May 2019 12:21:33 -0400 (EDT) [thread overview]
Message-ID: <1448366760.18406.1559146893765.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAEWVvOS6WyAkE+5GAyn_WEoFW_6h_fWbze-im0w7oqvXS-+dBw@mail.gmail.com>
----- On May 29, 2019, at 12:19 PM, Ravindra Kumar Meena <rmeena840 at gmail.com> wrote:
> On Fri, May 17, 2019 at 12:22 AM Mathieu Desnoyers < [
> mailto:mathieu.desnoyers at efficios.com | mathieu.desnoyers at efficios.com ] >
> wrote:
>> ----- On May 16, 2019, at 1:42 AM, Ravindra Kumar Meena [
>> mailto:rmeena840 at gmail.com | rmeena840 at gmail.com ] wrote:
>> > Hi LTTng developers,
>> > I have been selected at GSoC 2019 with organization RTEMs. My project is [
>>> [ https://devel.rtems.org/ticket/3696 | https://devel.rtems.org/ticket/3696 ] |
>> > [ https://devel.rtems.org/ticket/3696 | https://devel.rtems.org/ticket/3696 ] ]
>> > The objective of the project is to convert the trace data into CTF. The trace
>> > data is already generated by the system. All that is left is to convert the
>> > trace data into CTF. I am interested in CTF because I want to send it to trace
>> > compass for analysis.
>> > Any idea how can I achieve this?
>> If you intend to produce CTF traces natively from the target, you will want to
>> look into the barectf project [1].
>> However, if your goal is to do a post-processing phase to convert traces from
>> some existing format to CTF, you will want to look into the Babeltrace project
>> [2]
>> master branch which is in preparation for Babeltrace 2.0. The approach here
>> would be to create a Babeltrace 2 source plugin which reads your trace format
>> into
>> the Babeltrace 2 intermediate representation by using the APIs exposed to
>> plugins by Babeltrace 2. Babeltrace 2 has a generic CTF sink which can serialize
>> the resulting trace intermediate representation into CTF.
>> Thanks,
>> Mathieu
>> [1] [ https://github.com/efficios/barectf | https://github.com/efficios/barectf
>> ]
>> [2] [ https://diamon.org/babeltrace/ | https://diamon.org/babeltrace/ ]
> Thanks, Mathieu for the approach. I am trying to use the babeltrace and I read
> its documentation and but I nowhere found the examples of conversion from one
> format to CTF.
> The examples would make it more clear.
> Is it possible to convert the live trace stream into CTF stream with the current
> babeltrace?
With babeltrace 1.5.x: No.
With babeltrace master branch (currently in -pre stage before 2.0): Yes.
Thanks,
Mathieu
> Thanks
> --
> Ravindra Kumar Meena ,
> B. Tech. Computer Science and Engineering,
> [ https://www.iitism.ac.in/ | Indian Institute of Technology (Indian School of
> Mines) ] , Dhanbad
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20190529/e1cd68dc/attachment.html>
next prev parent reply other threads:[~2019-05-29 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 5:42 Ravindra Kumar Meena
2019-05-16 18:52 ` Mathieu Desnoyers
2019-05-29 16:19 ` Ravindra Kumar Meena
2019-05-29 16:21 ` Mathieu Desnoyers [this message]
2019-05-29 16:28 ` Ravindra Kumar Meena
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=1448366760.18406.1559146893765.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.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