No trace generated by example launch file
Hi,
So now I have the system running without throwing an error. But there is no trace generated in .ros/tracing
The output of the example launch is as follows:
$ ros2 launch tracetools_launch example.launch.py
[INFO] [launch]: All log files can be found below /home/user/.ros/log/2020-01-08-13-44-59-527375-user-ipc-2-9276
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [test_ping-1]: process started with pid [9285]
[INFO] [test_pong-2]: process started with pid [9286]
[test_ping-1] spinning
[test_ping-1] [INFO] [test_ping]: [output] some random pong string
[test_pong-2] spinning
[test_pong-2] [INFO] [test_pong]: [output] some random ping string
[INFO] [test_ping-1]: process has finished cleanly [pid 9285]
[INFO] [test_pong-2]: process has finished cleanly [pid 9286]
Expected behavior would be, that I now have a folder tracing with the corresponding trace. This is not the case.
For more output and still no trace:
(Not entirely sure if I use this correctly here, or should specify a launch file)
$ ros2 trace
UST tracing enabled (14 events)
kernel tracing enabled (4 events)
context (3 names)
writing tracing session to: /home/user/.ros/tracing/session-20200108134439
press enter to start...
press enter to stop...
stopping & destroying tracing session
Running the test if tracing is enabled returns true:
$ ros2 run tracetools status
Tracing enabled
edit:
During the build process LTTng is found:
stderr: tracetools
LTTng found: tracing enabled
The build was triggered by:
colcon build --symlink-install --cmake-args " -DWITH_LTTNG=ON"
Though i guess the last variable is not used anymore, just got that information from the ROS-I Talk
Edited by Lennart