I feel like this environment variable is more about the library than
about the project as a whole, like `LIBBABELTRACE2_INIT_LOG_LEVEL`.
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Change-Id: I19e5229fc64d54f2a4ff23ef36647ba78917b619
Reviewed-on: https://review.lttng.org/c/babeltrace/+/1554
Tested-by: jenkins <jenkins@lttng.org>
----
$ G_SLICE=always-malloc G_DEBUG=gc-friendly PYTHONMALLOC=malloc \
- BABELTRACE_NO_DLCLOSE=1 valgrind --leak-check=full \
+ LIBBABELTRACE2_NO_DLCLOSE=1 valgrind --leak-check=full \
--suppressions=/path/to/babeltrace/extras/valgrind/popt.supp app
----
the Python plugin provider (Valgrind will probably show a lot of errors
which originate from the Python interpreter anyway).
-`BABELTRACE_NO_DLCLOSE=1` makes libbabeltrace2 not close the shared
+`LIBBABELTRACE2_NO_DLCLOSE=1` makes libbabeltrace2 not close the shared
libraries (plugins) which it loads. You need this to see the appropriate
backtrace when Valgrind shows errors.
/*
* Valgrind shows incomplete stack traces when
* dynamically loaded libraries are closed before it
- * finishes. Use the BABELTRACE_NO_DLCLOSE in a debug
+ * finishes. Use the LIBBABELTRACE2_NO_DLCLOSE in a debug
* build to avoid this.
*/
- const char *var = getenv("BABELTRACE_NO_DLCLOSE");
+ const char *var = getenv("LIBBABELTRACE2_NO_DLCLOSE");
if (!var || strcmp(var, "1") != 0) {
#endif
shared_lib_handle->module = NULL;
#ifndef BT_DEBUG_MODE
} else {
- BT_LOGI("Not closing GModule because `BABELTRACE_NO_DLCLOSE=1`: "
+ BT_LOGI("Not closing GModule because `LIBBABELTRACE2_NO_DLCLOSE=1`: "
"path=\"%s\"", path);
}
#endif