Yoann, Sorry for the wait.
I created a corresponding barectf project issue here: <https://github.com/efficios/barectf/issues/19>. Can you answer the latest question there? Thank you for reporting this. Philippe Proulx Philippe Proulx On Fri, Nov 26, 2021 at 12:41 PM Yoann Farré via lttng-dev <lttng-dev@lists.lttng.org> wrote: > > Hello, > > > > I’m new in the world of tracing. And I have a question about barectf and > malformed trace event. > > > > For the context, I use the tool Papyrus to build UML models and then generate > C++ code. The code can be instrumented to generate CTF traces (with barectf) > and follow some relevant model elements. > > > > More precisely, I generated a trace and tried to read it with TraceCompass. > The traces seems to contains a malformed event. Unfortunately it avoids to > read the follow-up (if any). > > > > > > I also tried to read the trace with babeltrace which clearly shows that there > is a malformed event [1]. > > > > Can anyone give me some help to avoid generate malformed event / or to enable > to read the follow-up of the trace ? > > > > To be complete, I join the raw trace [2]. I can also provide the code which > produces this trace if it has any kind of interest. > > > > [1] error_babeltrace.txt > > [2] ctftrace04.zip > > > > Thanks for reading and your help. > > Regards. > > > > Yoann Farré. > > > > _______________________________________________ > lttng-dev mailing list > lttng-dev@lists.lttng.org > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
