[issue44719] Incorrect callable object crashes Python 3.11.0a0

Dennis Sweeney added the comment: Indeed, I got no crash on main after GH-27313. I also got no crash on 3.10 after GH-23568. Its backport to 3.9 (GH-24501) would have fixed this, but broke the stable ABI and was reverted. This was related to bpo-42500. I'm closing this "fixed". Feel free to

[issue44719] Incorrect callable object crashes Python 3.11.0a0

Dennis Sweeney added the comment: I think GH-27313 will fix this -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue44719] Incorrect callable object crashes Python 3.11.0a0

Dennis Sweeney added the comment: ### Simplified crasher from weakref import ref def f(): ref(lambda: 0, []) f() f() Running this in debug mode, I got a failed assertion at traceback.c, line 746, `assert(source_line);`. If that assertion is commented out,

[issue44719] Incorrect callable object crashes Python 3.11.0a0

New submission from Xinmeng Xia : This program can trigger "Aborted (core dumped)" on Python 3.9.0, Python 3.8.0, Python3.10.0a2. It trigger " segmentation fault" on the master (Python 3.11.0a0). == import weakref class Object: def __init__(self, arg):