Community
Participate
Working Groups
The goal is here to investigate and prototype tools enabling exploiting the trace information at the model level. It will require analyzing and defining new means (including as for example specific analyzing tools and visualization mechanisms) on how the trace information collected executing an application code generating from a model can be exploited at the model level in order to set up the application model.
If code generation from Qompass is used, it is possible to ebable tracing by using a specifc container service that intercepts the incoming and outgoing messages of a component. Thus, tracing currently supports the access of component services via a port. There are two tracing services, one for LTTng and one for OTF (open trace format). Model navigation is supported for LTTng. The instrumentation in the generated code adds the URI of the model element to the LTTng trace meta-data, as shown in the TRACEPOINT event declaration below. // declare trace point TRACEPOINT_EVENT(ClientServer_methodCall_port_ICompute_p, mult, TP_ARGS(const char *, instanceName, int, a, int, b), TP_FIELDS( ctf_string(instanceName, instanceName) ctf_integer(int, a, a) ctf_integer(int, b, b) ) ) TRACEPOINT_MODEL_EMF_URI(ClientServer_methodCall_port_ICompute_p, mult, "platform:/resource/org.eclipse.papyrus.qompass.modellibs.distribution/models/examples/ClientServer.uml#_4KiE8DLbEd2qeKRLMdIx_A") The tracing support is currently not described in the Qompass user guide. https://wiki.eclipse.org/Papyrus_Qompass This needs to be done, before this error can be clsoed.
