niklas/ros2_tracing
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
373 commits 1 branch 0 tags 929 KiB
Find a file
Christophe Bedard 6f9cc13902 Fix lint_cmake errors
2019-07-25 09:16:23 +02:00
doc Add space between ROS and 2 2019-07-01 11:08:00 +02:00
ros2trace 0.1.1 2019-07-16 10:53:31 +02:00
tracetools Rename option 2019-07-25 09:03:29 +02:00
tracetools_launch 0.1.1 2019-07-16 10:53:31 +02:00
tracetools_read 0.1.1 2019-07-16 10:53:31 +02:00
tracetools_test Fix lint_cmake errors 2019-07-25 09:16:23 +02:00
tracetools_trace 0.1.1 2019-07-16 10:53:31 +02:00
.gitlab-ci.yml Update CI config for build job 2019-07-25 09:03:39 +02:00
all.repos Update repo URLs after move to micro-ROS/ 2019-07-09 07:58:18 +00:00
instrumentation.repos Update repo URLs after move to micro-ROS/ 2019-07-09 07:58:18 +00:00
LICENSE Add license file 2019-06-18 08:53:46 +02:00
README.md Enable tracing by default if LTTng is available 2019-07-19 10:38:08 +02:00

README.md

tracetools

Tracing tools for ROS 2.

Building

If the TRACETOOLS_ENABLED option is disabled during build or if LTTng is not found, then this package will not do anything.

To enable tracing:

  1. Install LTTng with the Python bindings to control tracing and read traces: 
    $ sudo apt-add-repository ppa:lttng/stable-2.10
$ sudo apt-get update
$ sudo apt-get install lttng-tools lttng-modules-dkms liblttng-ust-dev
$ sudo apt-get install python3-babeltrace python3-lttng
    Note: the LTTng stable 2.10 PPA is used to get newer versions of the packages.
  2. Build 
    $ colcon build
  3. Source and check that tracing is enabled: 
    $ source ./install/local_setup.bash
$ ros2 run tracetools tracetools_status

Tracing

The steps above will not lead to trace data being generated, and thus they will have no impact on execution. LTTng has to be enabled. The packages in this repo provide two options.

Trace command

The first option is to use the ros2 trace command.

$ ros2 trace

By default, it will enable all ROS tracepoints and a few kernel tracepoints. The trace will be written to ~/.ros/tracing/session-YYYYMMDDHHMMSS. Run the command with -h for more information.

Launch file trace action

Another option is to use the Trace action in a launch file along with your Node action(s).

See this example launch file for more information.