This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dynamic-link/11787] Program with large TLS segments fail.


https://sourceware.org/bugzilla/show_bug.cgi?id=11787

Steven Schlansker <stevenschlansker at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stevenschlansker at gmail dot com

--- Comment #43 from Steven Schlansker <stevenschlansker at gmail dot com> ---
The JVM is having trouble too, see the following core-libs-dev discussion:

http://mail.openjdk.java.net/pipermail/core-libs-dev/2015-December/037557.html

If you link the JVM as a library and use thread local storage, it is very hard
for JVM internal threads to ensure that their stack is usable.

>From the Rust discussion, they link that the Go runtime had the exact same
problem.

How many languages are going to have to work around this broken behavior before
there is a glibc fix? :(

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]