STINNER Victor added the comment:
> This is arguably a bug in glibc, but Python can easily work around it by
> linking the core interpreter (the `python` executable and/or `libpython.so`)
> with libgcc_s at build time (`-lgcc_s`) on Linux. It will then be loaded
> already if and when it's
New submission from Zack Weinberg :
There are several existing issues (e.g. #18748 and #35866) where at least part
of the problem is that GNU libc tried to dlopen() `libgcc_s.so` at a moment
when that's not safe, e.g. during thread or process shutdown. This converts a
recoverable error into
