STINNER Victor <vstin...@redhat.com> added the comment:
You can try to use faulthandler.dump_traceback_later() with a file to get the traceback of the stuck threads. ------------------thread1------------------ ... !UuidCreate+0x1b00 ... !RegEnumKeyExW+0xbe ... !LookupPrivilegeValueA+0x84 !PyNamespace_New+0xd4 !PyCodec_LookupTextEncoding+0xb5 !PyObject_SetAttrId+0x21e ... !PyObject_CallMethod+0x3c !PyTime_MulDiv+0x47 !Py_InitializeMainInterpreter+0x95 !PyMainInterpreterConfig_Read+0x309 !PyMapping_SetItemString+0x306 !PyBytes_AsString+0x142 !Py_Main+0x52 !BaseThreadInitThunk+0xd This traceback doesn't make sense: * Py_Main() doesn't call directly PyBytes_AsString(). * PyTime_MulDiv shouldn't call PyObject_CallMethod(). * I don't see how PyNamespace_New() can call LookupPrivilegeValueA() ---------- nosy: +vstinner _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35418> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
