GLibC

  1. Bug #1757517
  2. Comment #47

Comment 47 for bug 1757517

Revision history for this message
In , stevenschlansker (stevenschlansker) wrote :

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? :(