When the symbols clashing with lttng-ust 2.12 are renamed to be suffixed
with "1", it becomes possible to run lttng-ust 2.12 and 2.13 in the same
process.
Leave those sanity checks in place for builds with
LTTNG_UST_CUSTOM_UPGRADE_CONFLICTING_SYMBOLS defined.
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Change-Id: I8664884bdc60043bf28b923786a16ee2ee3301a8
#include <urcu/compiler.h>
#include <urcu/system.h>
+#include <lttng/ust-config.h>
#include <lttng/tracepoint.h>
#include <lttng/ust-abi.h> /* for LTTNG_UST_ABI_SYM_NAME_LEN */
#include <lttng/ust-common.h>
}
}
+#ifdef LTTNG_UST_CUSTOM_UPGRADE_CONFLICTING_SYMBOLS
/*
* Use a symbol of the previous ABI to detect if liblttng-ust-tracepoint.so.0
* is loaded in the current process.
return -1;
}
+#else
+static void lttng_ust_tracepoint_check_soname_0(void) {}
+#endif
/**
* lttng_ust_tracepoint_provider_register - Connect a probe to a tracepoint
{
}
+#ifdef LTTNG_UST_CUSTOM_UPGRADE_CONFLICTING_SYMBOLS
/*
* Use a symbol of the previous ABI to detect if liblttng-ust.so.0 is loaded in
* the current process.
"The process is likely linked against different major soname of LTTng-UST which is unsupported. "
"The detection was triggered by canary symbol \"%s\"\n", __func__);
}
+#else
+static void lttng_ust_check_soname_0(void) {}
+#endif
/*
* sessiond monitoring thread: monitor presence of global and per-user