STINNER Victor <vstin...@python.org> added the comment:
"Segmentation fault with (...) threads (...) getaddrinfo"
Aha, another victim on a getaddrinfo() implementation which is not thread safe.
See this code in Modules/socketmodule.c:
/* Lock to allow python interpreter to continue, but only allow one
thread to be in gethostbyname or getaddrinfo */
#if defined(USE_GETHOSTBYNAME_LOCK)
static PyThread_type_lock netdb_lock;
#endif
Can you please check if your Python was built with HAVE_GETHOSTBYNAME_R?
$ python3
Python 3.9.1 (default, Jan 20 2021, 00:00:00)
[GCC 10.2.1 20201125 (Red Hat 10.2.1-9)] on linux
>>> import sysconfig; repr(sysconfig.get_config_var('HAVE_GETHOSTBYNAME_R'))
'1'
Modules/socketmodule.c is full of #ifdef involving macOS...
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue39853>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
