From: eeppeliteloop@gmail.com (Philippe Proulx)
Subject: [lttng-dev] Are arrays allowed in event payload?
Date: Mon, 25 Sep 2017 15:56:21 -0400 [thread overview]
Message-ID: <CAB4xu_3pd=NLVZgYyCXH5Hzr1dejUx9KR3OKp1MEOMdXpg7-KA@mail.gmail.com> (raw)
In-Reply-To: <CAAuy2ASF_rf1a9iuo=XKKPriVgEPGues-sQ-HyMOdg7F+VjC7g@mail.gmail.com>
On Mon, Sep 25, 2017 at 3:41 PM, Nwafor, Ebelechukwu
<ebelechukwu.nwafor at bison.howard.edu> wrote:
> Hello All
>
> I am new to barectf. I am trying to define my yaml configuration and i keep
> getting an error whenever i try to compile my configuration. I was wondering
> if arrays are allowed in the event payload section and if yes how are they
> defined?
What is the error?
As per the project's README.md:
> CTF compound types (array, sequence, structure, variant) are not
> supported yet, except at some very specific locations in the metadata.
In fact, the only "very specific location" is the trace packet header's
`uuid` field which must be an array of 16 8-bit integers. This `uuid`
field is handled as a special case when generating the tracer:
<https://github.com/efficios/barectf/blob/v2.2.1/barectf/gen.py#L852>.
There's currently no generic way in barectf to generate C code which
writes an array of elements to the current packet buffer.
Supporting compound types is a feature request which often comes up (in
LTTng-UST too).
Phil
>
>
> Thanks.
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
prev parent reply other threads:[~2017-09-25 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 19:41 Nwafor, Ebelechukwu
2017-09-25 19:56 ` Philippe Proulx [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_3pd=NLVZgYyCXH5Hzr1dejUx9KR3OKp1MEOMdXpg7-KA@mail.gmail.com' \
--to=eeppeliteloop@gmail.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