[Bug 1618201] Re: deadlock in lttng_ust_init

2017-03-13 Thread Michał Sawicz
** No longer affects: qtmir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init To manage notifications about this bug go to:

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-12-08 Thread Daniel d'Andrada
** Changed in: qtmir (Ubuntu) Status: Triaged => Fix Released ** Changed in: qtmir Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title:

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-13 Thread Michael Jeanson
Looks like a glibc 2.21 bug with TLS constructors, see: https://bugzilla.redhat.com/show_bug.cgi?id=1223055 Seems to be fixed upstream by these commits: https://github.com/bminor/glibc/commit/e400f3ccd36fe91d432cc7d45b4ccc799dece763

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-08 Thread Daniel d'Andrada
libc6 2.21-0ubuntu4.0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init To manage notifications about this bug go to:

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-08 Thread Mathieu Desnoyers
What is your glibc version ? You provided your libglib version which is unrelated to lttng-ust. Or are you using Android bionic libc... ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title:

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-08 Thread Daniel d'Andrada
liblttng-ust 2.7.1-1~vividoverlay1 libglib2.0 2.44.1-1ubuntu1 About comments #4 and #5: what seems more relevant is actually ubuntu release/pkg versions since my desktop runs xenial+stable-phone-overlay whereas my arm devices run vivid+stable-phone-overlay. -- You received this bug

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-08 Thread Daniel d'Andrada
But on CI it also deadlocks in amd64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init To manage notifications about this bug go to:

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-08 Thread Daniel d'Andrada
It might have something to do with arm or chroot envs (likely what CI does) as tests run fine on my amd64 desktop but deadlock in a chroot on an arm device (like mako or flo). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-06 Thread Mathieu Desnoyers
It seems odd that touching a shared object TLS (which triggers a TLS fixup) from a constructor would deadlock. Which version of glibc are you using ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-06 Thread Simon Marchi
Which version of liblttng-ust is that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init To manage notifications about this bug go to:

[Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-06 Thread Gerry Boland
This issue was worked around, but with a far-from-ideal solution ** Also affects: lttng-ust (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New => Triaged ** Changed