Summary: | [Trace] Papyrus shall assist the user to exploit trace information at the model level | ||
---|---|---|---|
Product: | [Modeling] Papyrus | Reporter: | Camille Letavernier <cletavernier> |
Component: | Others | Assignee: | Ansgar Radermacher <ansgar.radermacher> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | lars.gelin, papyrus-bugs, patrik |
Version: | unspecified | Keywords: | plan |
Target Milestone: | --- | Flags: | rschnekenburger:
kepler+
|
Hardware: | All | ||
OS: | All | ||
Whiteboard: | Miscellaneous |
Description
Camille Letavernier
2013-02-04 07:55:15 EST
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. |