[issue42763] Exposing a race in the "_warnings" resulting Python parser crash

Change by Irit Katriel : -- versions: +Python 3.11 -Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42763] Exposing a race in the "_warnings" resulting Python parser crash

Xinmeng Xia added the comment: Now I see. By the way, I think this case should be moved back to "cpython/Lib/test/crashers/" since the bug still exists. It is not fixed completely, the old case is outdated. I suggest we can put the new case into directory "crashers". --

[issue42763] Exposing a race in the "_warnings" resulting Python parser crash

Steve Stagg added the comment: If we take your minimal example (that /sometimes/ crashes), and look at what python is doing: import threading t = threading.Thread(target=1, daemon=True).start() --- The main thread does the following: M1. Startup interpreter, parse code M2. Import &

[issue42763] Exposing a race in the "_warnings" resulting Python parser crash

Xinmeng Xia added the comment: Thank you, but I don't think this is a duplicate of issue42717. This crash is probably caused by the parameter "target" of Thread. "Target" accept the "callable object". Defaults to None. In this program, it's assigned to a "Int object". I think a pre-checking

[issue42763] Exposing a race in the "_warnings" resulting Python parser crash

Steve Stagg added the comment: Looks like a duplicate of issue42717. Causing a daemonic thread to terminate while doing IO will trigger the above abort -- nosy: +stestagg ___ Python tracker

[issue42763] Exposing a race in the "_warnings" resulting Python parser crash

New submission from Xinmeng Xia : This program is initially from "cpython/Lib/test/crashers/warnings_del_crasher.py" in Python 2.7. The original case is fixed for all version of Python and removed from "crashers" directory. However, if we replace the statement "for i in range(10):" of