Closed cochicde closed 3 weeks ago
we have a Tracer ? @azoitl this would be VERY helpful. such a Thing which X/Y Coordinates and writing Diagramms of Variables ? I am Impressed !
we have a Tracer ? @azoitl this would be VERY helpful. such a Thing which X/Y Coordinates and writing Diagramms of Variables ? I am Impressed !
I don't think this is what you can to with that. Currently tracing is more for getting deeper insights on what is going on. But it heavily impacts performance and is not suitable for non-linux platforms.
ahhhhhhhhhhhhhhhh ....
so this would be a totally different thing: having a Chart Draw module in IDE, to make Plots during a Watch ?
ahhhhhhhhhhhhhhhh ....
so this would be a totally different thing: having a Chart Draw module in IDE, to make Plots during a Watch ?
yes
This PR is part a branch with some other things, so some things are still not used here. The folllowing was done here:
barectf
tracer was removed from the main code and hidden inBarectfPlatformFORTE
. To do that, aCForteTracer
typedef was created which can be set to other tracers during compilation time.BarectfPlatformFORTE
(and others tracers) have methods such astraceInstanceData
,traceReceiveInputEvent
, etc. which mirror the ones frombarectf
. The Function Blocks then call these methods inCForteTracer
class.EventMessage
which contains the same information as thebarectf
traces. This is only compile if the tracer tests are enabled.BarectfPlatformFORTE
and the internal tracer, which allows selecting one or the other during runtime. This is the default tracer if tracer tests are enabled.babeltrace2
was moved out of theEventMessages
and this factory allows creatingEventMessages
from thebt_field
(and other) types defined bybabeltrace2
.The main idea of this new code is to be able generate traces using
barectf
but also directly into memory and be able to have the same class to compare them (EventMessage
)