[issue32421] Keeping an exception in cache can segfault the interpreter

Yonatan Zunger added the comment: Apologies -- I've been completely swamped and haven't had time to build a repro case. I don't think I have enough state on the way I found this to reconstruct it easily right now, so I'll close it and re-open if I find it again. --

[issue32421] Keeping an exception in cache can segfault the interpreter

Terry J. Reedy added the comment: I repeated Julian's test with installed 3.7.0b2 on Windows 10 and there is no crash when running either from a command line or from an IDLE editor. So either the issue has been fixed since 3.6.2, or it is specific to some undisclosed

[issue32421] Keeping an exception in cache can segfault the interpreter

Julien Palard added the comment: Serhiy: Sorry the ∈ comes from emacs' pretty-mode, I should copy from outside emacs. Version tested are listed in my previous message. -- ___ Python tracker

[issue32421] Keeping an exception in cache can segfault the interpreter

Serhiy Storchaka added the comment: > for _ ∈ range(5): What version of Python are you using? -- ___ Python tracker

[issue32421] Keeping an exception in cache can segfault the interpreter

Terry J. Reedy added the comment: Yonathon, when replying by email, please delete the quoted message, except possibly for a specific line, as it is redundant noise when posted on the web page. -- nosy: +terry.reedy ___ Python

[issue32421] Keeping an exception in cache can segfault the interpreter

Yonatan Zunger added the comment: 3.6.2. But Nick Coghlan pointed out elsewhere that the underlying issue is more likely to be one of the other objects being pinned in-memory because of the traceback, so the exception may actually be just an incidental thing. I'm going to have

[issue32421] Keeping an exception in cache can segfault the interpreter

Julien Palard added the comment: Tested with: @memoize() def foo(x): raise Exception("From foo") for _ ∈ range(5): try: foo(42) except Exception as err: print(err) using a python 3.5.4, 3.6.4, and

[issue32421] Keeping an exception in cache can segfault the interpreter

Yonatan Zunger added the comment: It's just a clean version of reraise. Part of the six (Py2/Py3 compatibility) library, but pretty useful on its own anyway. On Sun, Dec 24, 2017 at 8:37 PM, Nitish wrote: > > Nitish added

[issue32421] Keeping an exception in cache can segfault the interpreter

Nitish added the comment: What is six.reraise in except block? -- nosy: +nitishch ___ Python tracker ___

[issue32421] Keeping an exception in cache can segfault the interpreter

Change by Josh Holland : -- nosy: +anowlcalledjosh ___ Python tracker ___ ___

[issue32421] Keeping an exception in cache can segfault the interpreter

Change by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue32421] Keeping an exception in cache can segfault the interpreter

New submission from Yonatan Zunger : Using the following decorator to memoize a function causes the interpreter to segfault on exit if any exceptions were stored in the cache. Changing the bad line to instead store copy.copy(e) makes the problem go away. Almost certainly