niklas/ros2_tracing
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
290 commits 1 branch 0 tags 929 KiB
Find a file
Ingo Lütkebohle 52b80798c8 Copy build dir into docker container.
2019-07-03 19:18:05 +00:00
doc Add space between ROS and 2 2019-07-01 11:08:00 +02:00
docker-ci-base Copy build dir into docker container. 2019-07-03 19:18:05 +00:00
ros2trace Fix lint and formatting errors 2019-06-24 16:13:42 +02:00
tracetools Remove whitespace 2019-06-28 14:01:20 +02:00
tracetools_launch Use ping pong nodes in example launch file 2019-06-28 09:36:22 +02:00
tracetools_read Make CI only build necessary packages from source 2019-06-25 11:30:43 +02:00
tracetools_test Add option to make ping pong test run over and over 2019-06-28 09:35:13 +02:00
tracetools_trace Fix trace args description 2019-06-28 08:58:01 +02:00
.gitlab-ci.yml Move build of preparatory packages into docker image. 2019-07-03 19:07:45 +00:00
ci_source_deps.repos Re-order CI dependencies list 2019-07-03 13:10:09 +02:00
instrumentation.repos Make CI only build necessary packages from source 2019-06-25 11:30:43 +02:00
LICENSE Add license file 2019-06-18 08:53:46 +02:00
README.md Fix wording in README 2019-06-27 16:36:24 +02:00

README.md

tracetools

Tracing tools for ROS 2.

Building

If tracing is not enabled when building, 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 with the WITH_LTTNG flag: 
    $ colcon build --cmake-args " -DWITH_LTTNG=ON"
  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 /tmp/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.