Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Writing a babeltrace output plugin
Date: Tue, 3 Apr 2012 08:57:54 -0400	[thread overview]
Message-ID: <20120403125754.GC14534@Krystal> (raw)
In-Reply-To: <524C960C5DFC794E82BE548D825F05CF29D8C6@EU-MBX-04.mgc.mentorg.com>

* Oestman, Fredrik (Fredrik_Oestman at mentor.com) wrote:
> Hello,
> 
> 
> I've fairly easily manged to add a new text-based output format to babeltrace by cloning the existing ctf-text code and making changes to it. Thanks to the registration mechanism it was also easy to get the program to recognize the new format on the command line.
> 
> Now, the problem I have with my new text format is that it completely lacks metadata.
> 
> What would be the intended way to provide an output format with metadata, or from where should I preferably collect metadata when writing a trace log in a new format?
> 
> Thanks in advance for any advice!

You'll have to either use the public API (see which files are installed
by babeltrace into your system): this is the preferred solution,
although there might be some missing metadata information (it's made to
support a trace reader, not a trace converter that would have to
regenerate the entire metadata).

The second solution is to look at include/babeltrace/ctf-ir/metadata.h
in-tree, and include/babeltrace/types.h (also in-tree). Those files
contain almost all the metadata of the CTF trace read, so you should be
able to extract your own metadata from those.

Hoping this helps,

Best regards,

Mathieu

> 
> 
> Cheers,
> 
> Fredrik ?stman
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com



  reply	other threads:[~2012-04-03 12:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 10:55 [lttng-dev] Babeltrace ctf-text duplicated error message Oestman, Fredrik
2012-04-03 11:35 ` [lttng-dev] Writing a babeltrace output plugin Oestman, Fredrik
2012-04-03 12:57   ` Mathieu Desnoyers [this message]
2012-04-03 13:31     ` Oestman, Fredrik
2012-04-03 13:33       ` Mathieu Desnoyers
2012-04-03 13:34         ` Mathieu Desnoyers
2012-04-03 14:06           ` Oestman, Fredrik
2012-04-03 14:10             ` Mathieu Desnoyers
2012-04-03 14:21               ` Julien Desfossez
2012-04-04  7:00                 ` Oestman, Fredrik
2012-04-17  6:57     ` Oestman, Fredrik
2012-04-17 15:05       ` Mathieu Desnoyers
2012-04-17 15:30         ` Alexandre Montplaisir
2012-04-17 15:44           ` Matthew Khouzam
2012-04-17 15:48           ` Mathieu Desnoyers
2012-04-03 12:53 ` [lttng-dev] Babeltrace ctf-text duplicated error message 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=20120403125754.GC14534@Krystal \
    --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