Issue 692776: new.function() leads to segfault (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/38042

classification

Title: new.function() leads to segfault
Type: Stage:
Components: Interpreter Core Versions: Python 2.2

process

Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: jhylton Nosy List: exarkun, jhylton, mwh
Priority: high Keywords:

Created on 2003-02-25 08:04 by exarkun, last changed 2022-04-10 16:07 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
segfault.py exarkun,2003-02-25 08:05
Messages (5)
msg14803 - (view) Author: Jean-Paul Calderone (exarkun) * (Python committer) Date: 2003-02-25 08:04
If a code object which requires a closure is passed to new.function(), a segfault (Python/ceval.c:2578). This seems to be fixed in 2.3. Attached is a short code example that demonstrates the behavior.
msg14804 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2003-02-25 09:31
Logged In: YES user_id=6656 You're right. I guess the fix is to backport the extra 'closure' argument from 2.3. I'll look into this.
msg14805 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2003-04-09 10:48
Logged In: YES user_id=6656 Jeremy, is this easy for you to fix? It's fiddlier than I expected.
msg14806 - (view) Author: Jeremy Hylton (jhylton) (Python triager) Date: 2003-04-09 18:57
Logged In: YES user_id=31392 I think I can swap in the state without too much pain.
msg14807 - (view) Author: Jeremy Hylton (jhylton) (Python triager) Date: 2003-05-22 18:11
Logged In: YES user_id=31392 Backported for 2.2.3.
History
Date User Action Args
2022-04-10 16:07:06 admin set github: 38042
2003-02-25 08:04:23 exarkun create