From: RADERMACHER Ansgar via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] [barectf] model.emf.uri
Date: Mon, 1 Feb 2021 09:12:24 +0000 [thread overview]
Message-ID: <386C5D4D5C53C24CBC2C60CAAFD2136A5B4A40A0@EXDAG0-B1.intra.cea.fr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1019 bytes --]
Hello,
we're currently working on CTF code instrumentation in the C++ code generation from Papyrus. Unlike in a previous version, we use BareCTF.
In this context, the metadata tag "model.emf.uri" can contain the URI of the element to trace. This works fine in TraceCompass, if we manually add the URI to the metadata, as shown below. But I have not been able to add an entry to BareCTF's config.yaml that produces the model.emf.uri in the generated metadata file. Is it possible?
I could not find an suitable example in the documentation - I experimented with the "specific-context-field-type", but it also adds a parameter to the generated C code functions which is not what I want.
Best regards
Ansgar
...
event {
stream_id = 0;
id = 1;
name = "state_C1_FirstState_state";
model.emf.uri = "platform:/resource/DemoTrace/DemoTrace.uml#_AVreJm9fEeqJeI8mbLLRcg";
fields := struct {
string {
encoding = UTF8;
} instanceId;
} align(1);
};
[-- Attachment #1.2: Type: text/html, Size: 1826 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
next reply other threads:[~2021-02-01 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 9:12 RADERMACHER Ansgar via lttng-dev [this message]
2021-02-01 13:02 ` Philippe Proulx via lttng-dev
2021-02-05 11:05 ` Ansgar Radermacher via lttng-dev
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=386C5D4D5C53C24CBC2C60CAAFD2136A5B4A40A0@EXDAG0-B1.intra.cea.fr \
--to=lttng-dev@lists.lttng.org \
--cc=Ansgar.RADERMACHER@cea.fr \
/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