[Bug 1757517] Re: An unused thread-local memory allocation can cause library calls to segfault.

2019-03-25 Thread Bug Watch Updater
Launchpad has imported 48 comments from the remote bug at https://sourceware.org/bugzilla/show_bug.cgi?id=11787. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Bug 1757517] Re: An unused thread-local memory allocation can cause library calls to segfault.

2018-12-08 Thread Adam Conrad
** Also affects: glibc via https://sourceware.org/bugzilla/show_bug.cgi?id=11787 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757517 Title: An

[Bug 1757517] Re: An unused thread-local memory allocation can cause library calls to segfault.

2018-03-21 Thread Florian Weimer
Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=11787 ** Bug watch added: Sourceware.org Bugzilla #11787 https://sourceware.org/bugzilla/show_bug.cgi?id=11787 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1757517] Re: An unused thread-local memory allocation can cause library calls to segfault.

2018-03-21 Thread Moosfet
To see the problem in Jack, this example from the Jack project can do it: https://github.com/jackaudio/example-clients/blob/master/simple_client.c Just add the "static __thread anything[8 * 1048576]" to it and previously-working code begins doing this instead: Cannot create thread res = 22