[issue40965] Segfault when importing unittest module via C API

STINNER Victor added the comment: I mark this issue as a duplicate of bpo-40294. Right, please upgrade to Python 3.8.3 which includes the fix. -- nosy: +vstinner resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Use-after-free crash if multiple inter

[issue40965] Segfault when importing unittest module via C API

The Comet added the comment: Thanks for the input! I should have been more specific. I was running python 3.8.2 when I got this segfault. I upgraded to 3.8.3 and the issue is no longer present, so it seems this has already been fixed. -- ___ Pyth

[issue40965] Segfault when importing unittest module via C API

Steve Stagg added the comment: Fix was here: a75e730075 bpo-40294: Fix _asyncio when module is loaded/unloaded multiple times (GH-19542) Backport commit was: 6b0ca0aeab04d7b7b54086248ca9d5e70f770f2f >From my end, the issue seems to be resovled on tag v.3.8.3 -- ___

[issue40965] Segfault when importing unittest module via C API

Steve Stagg added the comment: I was able to reproduce, follows is the raw LLDB output, I don't think this fails on master, will try some bisecting: * thread #1, name = 'runtest', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x77079ae7 _asyncio.cp

[issue40965] Segfault when importing unittest module via C API

Steve Stagg added the comment: This appears to have been introduced in 13915a3100 bpo-36356: Fix memory leak in _asynciomodule.c (GH-16598). Cannot reproduce on master -- ___ Python tracker __

[issue40965] Segfault when importing unittest module via C API

Christian Heimes added the comment: It would be helpful if you could provide a C stacktrace. I use gdb to create a stacktrace. You may have to install additional debug symbols. -- nosy: +christian.heimes ___ Python tracker

[issue40965] Segfault when importing unittest module via C API

Change by Brett Cannon : -- title: Segfault when importing unittest module -> Segfault when importing unittest module via C API ___ Python tracker ___

[issue40965] Segfault when importing unittest module

hai shi added the comment: Thanks for your report. I am not catch this segfault in my python compiler. I test your example in: Python 3.8.3 (v3.8.3:6f8c832) Python 3.9.0b3 (v3.9.0b3-dirty:b484871) Python 3.10.0a0 (heads/master-dirty:1c209e3) -- nosy: +shihai1991 _

[issue40965] Segfault when importing unittest module

New submission from The Comet : The following program will segfault the interpreter: #include int main() { Py_Initialize(); PyRun_SimpleString("import unittest"); Py_Finalize(); Py_Initialize(); PyRun_SimpleString("import unittest"); /* segfault here */ Py_Finalize();