* [lttng-dev] Parsing in-memory CTF packets with babeltrace2
@ 2022-03-02 22:18 Jon Lamb via lttng-dev
0 siblings, 0 replies; only message in thread
From: Jon Lamb via lttng-dev @ 2022-03-02 22:18 UTC (permalink / raw)
To: lttng-dev
[-- Attachment #1.1: Type: text/plain, Size: 1171 bytes --]
Hi,
I'm working on an program that is to receive CTF stream packets
and convert the contained events to a different format.
After reading through the babeltrace2 C API docs, I'm not
sure if it's possible to access the internal AST and parser
utilities used by the internal plugins, either manually
or through a source component plugin.
With a metadata text file at hand, is there a way to parse
CTF stream packet sitting in memory?
I'm trying to avoid having to write the in-memory packets to disk
first, and then use the source.ctf.fs component class to read them
back in as babeltrace2 API types.
For context, I have a few micros instrumented with barectf.
Depending on the deployment mode, I'm either sending CTF stream
packets out over serial or reading a ring buffer of packets via JTAG.
I can see this also being useful in a couple other dimensions I'd
eventually like to consider too:
* Implementing something lttng-relayd friendly for live viewer support
(parsing some of the packet header fields)
* Stream clock overflow bookkeeping (it'd let me reduce the probe effect of
have to manage a 32 or 64 bit clock on a 16 bit MCU)
Best,
Jon
[-- Attachment #1.2: Type: text/html, Size: 3743 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-03-02 22:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-02 22:18 [lttng-dev] Parsing in-memory CTF packets with babeltrace2 Jon Lamb via lttng-dev
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.