New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
infinite recursion in PyErr_WriteUnraisable #49473
Comments
Here is an example of pure Python code which can cause the interpreter I can reproduce the problem in 2.6.0 and 2.6.1 but not in 2.5.2. The __getattr__ function in this example is interesting in that it Added to the mix we have sys.stderr replaced by an instance with a write Here is a snippet of the call stack from gdb showing the recursion cycle #9 0x00000000004a442c in PyErr_WriteUnraisable (obj=0x64ae40) |
I believe that this problem was introduced in subversion revision 65319. |
sorry I meant revision 65320 |
Hi amaury, I am copying you into this issue because I think it was |
python 3.0 does not crash. And it has better code for infinite recursion Martin, your comments are welcome. Are there compatibility issues? |
Amaury, there is a funny bug in the 3.0 implementation with very low |
yes, let's add this change to the backport. |
As already mentioned, the backport patch isn't up to date. |
Could the experts who have previously commented please advise as to whether this issue should be open, closed or whatever. |
Works fine under 2.7-3.2. Not sure this is worth fixing in 2.6. |
On 2.7 prints two 42, on 3.x fails (RuntimeError: maximum recursion depth exceeded in comparison) on first call. 2.6 out of date for non-security fix. |
Ok, so I would say this whole issue is out of date now, since maintained branches don't show the issue. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: