For the record it is not a glibc bug. It is a defect in the loaded libraries, they should not require TLS. Fundamentally it's a defect that we allowed developers to build shared libraries with static TLS in the first place.
I will keep debugging this issue here and we'll get to a resolution.
(In reply to Ankur Sinha (FranciscoD) from comment #21) /bugzilla. redhat. com/show_ bug.cgi? id=1124987
> Hi,
>
> I seem to have run into the glibc bug too. I've filed a new bug here:
>
> https:/
For the record it is not a glibc bug. It is a defect in the loaded libraries, they should not require TLS. Fundamentally it's a defect that we allowed developers to build shared libraries with static TLS in the first place.
I will keep debugging this issue here and we'll get to a resolution.