Ok, I have an idea. content-hub links to libubuntu-app-launch.so, which links to liblttng-ust.so. On load of liblttng-ust.so, it registers 2 tracepoint providers by default: ust_baddr_statedump and lttng_ust_tracef. These are causing our repeating error messages.
Ok, I have an idea. content-hub links to libubuntu- app-launch. so, which links to liblttng-ust.so. On load of liblttng-ust.so, it registers 2 tracepoint providers by default: ust_baddr_statedump and lttng_ust_tracef. These are causing our repeating error messages.
Instead, I think we need to refactor UAL to dynamically load liblttng-ust.so, instead of linking to it, and dlload it when tracing is desired. See the strangely-named "Dynamic linking" section of the doc: www.lttng. org/docs/ #doc-building- tracepoint- providers- and-user- application
http://
This is what Mir is doing, and works well there. See bazaar. launchpad. net/~mir- team/mir/ development- branch/ view/head: /src/common/ report/ lttng/tracepoin t_provider. cpp
http://