LTTng » LTTng-tools

The lttng-tools project is configured as such:

./configure --with-consumerd32-libdir=/usr/local/lib32 --with-consumerd32-bin=/usr/local/lib32/lttng/libexec/lttng-consumerd

Config.h does include definition for consumerd32 bit

/* Location of the 32-bit consumerd executable. */
#define CONFIG_CONSUMERD32_BIN "/usr/local/lib32/lttng/libexec/lttng-consumerd" 

/* Search for consumerd 32-bit libraries in this location. */
#define CONFIG_CONSUMERD32_LIBDIR "/usr/local/lib32" 

On start the sessiond ignore those paths:

DEBUG1 - 14:57:13.370775164 [113567/113567]:     consumerd32 path:              /home/vagrant/.lttng/ustconsumerd32
DEBUG1 - 14:57:13.370793022 [113567/113567]:     consumerd32 bin path:          Unknown
DEBUG1 - 14:57:13.370825408 [113567/113567]:     consumerd32 lib dir:           Unknown

The code does not use CONFIG_CONSUMERD32_BIN anywhere.

Commit e6142f2e647e83238b1e399b1264e8adb05409f9 seems to have removed the code that used CONFIG_CONSUMERD32_BIN without providing an equivalent.

commit e6142f2e647e83238b1e399b1264e8adb05409f9
Author: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Date:   Thu Nov 9 17:46:54 2017 -0500

    centralize sessiond config option handling

    Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>

-static const char *consumerd32_bin = CONFIG_CONSUMERD32_BIN;
-static const char *consumerd64_bin = CONFIG_CONSUMERD64_BIN;
-static const char *consumerd32_libdir = CONFIG_CONSUMERD32_LIBDIR;
-static const char *consumerd64_libdir = CONFIG_CONSUMERD64_LIBDIR;

Using the command line works fine:

lttng-sessiond -vvv --verbose-consumer --consumerd32-libdir=/usr/local/lib32 --consumerd32-path=/usr/local/lib32/lttng/libexec/lttng-consumerd

Not sure if we want to use the path provided by configure or simply change the documentation to indicate that the paths must be passed either via the env or on the command line.