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: http://www.lttng.org/docs/#doc-building-tracepoint-providers-and-user-application This is what Mir is doing, and works well there. See http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/src/common/report/lttng/tracepoint_provider.cpp ** Changed in: content-hub (Ubuntu) Status: New => Invalid ** Also affects: ubuntu-app-launch (Ubuntu) Importance: Undecided Status: New ** Summary changed: - liblttng-ust0 Error opening shm /lttng-ust-wait-5 + liblttng-ust0 Error opening shm /lttng-ust-wait-5 - do not link liblttng-ust! ** Changed in: platform-api Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404302 Title: liblttng-ust0 Error opening shm /lttng-ust-wait-5 - do not link liblttng-ust! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1404302/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
