From: Philippe Proulx via lttng-dev <lttng-dev@lists.lttng.org>
To: "Yoann Farré" <yoann.farre@cil4sys.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [barectf] How to debug a malformed trace event?
Date: Tue, 7 Dec 2021 12:24:34 -0500 [thread overview]
Message-ID: <CAB4xu_0KK5cLiUycoxgfx+He6WO_=2JV6oEx_CuG3EMr2f9dqw@mail.gmail.com> (raw)
In-Reply-To: <PR3PR08MB5579AFB7793FED4AA03989BAA5639@PR3PR08MB5579.eurprd08.prod.outlook.com>
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
prev parent reply other threads:[~2021-12-07 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 17:23 [lttng-dev] [barectf] How to debug a malformed trace event? Yoann Farré via lttng-dev
2021-12-07 17:24 ` Philippe Proulx via lttng-dev [this message]
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='CAB4xu_0KK5cLiUycoxgfx+He6WO_=2JV6oEx_CuG3EMr2f9dqw@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=eeppeliteloop@gmail.com \
--cc=yoann.farre@cil4sys.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;
as well as URLs for NNTP newsgroup(s).