https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109634
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
I remember Glibc used to issue a readable diagnostic in that case ("cannot
allocate memory in static TLS block"). Worth reporting to Glibc if that part
regressed and the diagnostic is no longer available (at least I don't see it in
the linked Github issue).
What is actually happening here? Valgrind catches a null pointer dereference,
but where is that null coming from? Is the dynamic linker invoking constructors
with TLS pointer set to null, instead of aborting?
