LTTng » LTTng-tools

Greetings,

After going through the LTTng docs on how to build and install I chose to make a custom build of v2.10 (the yum version in my OS, Centos 7, is much older). Because I am only interested in a minimal LTTng libset sufficient for userspace tracing, I chose to do this via the vlttng tool and specifically with this command:

vlttng -p babeltrace-stable-1.5 -p lttng-tools-stable-2.10 -p lttng-ust-stable-2.10 -p urcu-stable-0.10 my_env

The resulting build appears to be fully functional except the headers contain no definition of LTTNG_TRACEPOINT_ENUM even though I can find sub-macros like ctf_enum(). After searching through the git sources I confirmed that this macro is defined in the lttng-modules project. I am not sure if this is by design or is an issue with the particular combination of projects I chose in vlttng.

It seems to me that if LTTng enums are fully supported by lttng-tools (seems like they should be, since this is a CTF feature), the LTTNG_TRACEPOINT_ENUM should be available without having to also build lttng-modules.

Further details:

>uname -a: Linux <host> 3.10.0-693.11.6.el7.x86_64 #1 SMP Thu Jan 4 01:06:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>cat /etc/centos-release: CentOS Linux release 7.4.1708 (Core)

LTTng version: 2.10, built as shown above

Cheers,
Vlad