Hi, So I wrote a draft of Rust lib above ctf-writer, using the apis as demonstrated in the ctf-writer test For deployment I wanted to use "libbabeltrace2-ctf-writer.so" in the "libbabeltrace2-dev" package but I could not locate the matching includes in there or in the other babeltrace 2 packages Did I miss them somewhere ? Should I have plugged in at another level in babeltrace2 ?
Best regards, Charles ----- Mail original ----- De: chafray...@free.fr À: "Mathieu Desnoyers" <mathieu.desnoy...@efficios.com> Cc: lttng-dev@lists.lttng.org Envoyé: Lundi 16 Janvier 2023 10:38:28 Objet: Re: [lttng-dev] LTTng UST structure support Hi Mathieu, Thanks for your reply :) I'll stick to bt2 modules in the meantime then I'll already be saving a ton of time with those and the CTF spec which is great ! Best regards, Charles ----- Mail original ----- De: "Mathieu Desnoyers" <mathieu.desnoy...@efficios.com> À: chafray...@free.fr, lttng-dev@lists.lttng.org Envoyé: Jeudi 12 Janvier 2023 21:10:57 Objet: Re: [lttng-dev] LTTng UST structure support On 2023-01-09 09:02, chafraysse--- via lttng-dev wrote: > Hi, > > I'm looking for a CTF writer to serialize instrumentations in an > embedded Linux/Rust framework > LTTng UST looked like a very strong option, but I want to serialize > structures as CTF compound type structures and I did not see those > supported in the doc or api This is correct. I am currently working on a new project called "libside" (see https://git.efficios.com/?p=libside.git;a=summary) which features support for compound types. However, we still need to do the heavy-lifting implementation work of integrating this with LTTng-UST. This is the plan towards supporting compound types in LTTng-UST. > I'd love to have confirmation that I did not just miss something :) > If LTTng UST is out for me I will probably try to use the ctf-writer > module of babeltrace 2 instead For now the ctf-writer modules of bt2 would be an alternative to consider, but remember that it is not designed for low-impact tracing such as lttng-ust. So it depends on how much tracer overhead/runtime impact you can afford in your use-case. Thanks, Mathieu > > Best regards, > > Charles > _______________________________________________ > lttng-dev mailing list > lttng-dev@lists.lttng.org > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev -- Mathieu Desnoyers EfficiOS Inc. https://www.efficios.com _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
