[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

Terry J. Reedy added the comment: This is one of four essentially duplicate issues #6028, #7338, #13644. #6028 has a proposed patch. -- nosy: +terry.reedy resolution: -> duplicate status: open -> closed versions: +Python 3.3 -Python 3.0 ___ Python t

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

kai zhu added the comment: just submitted a nearly identical bug (#7338) b4 checking for this one. so u think it works correctly up to the 2nd N+50 check. can someone give a reason y we should crash after that instead of throwing a fallback RuntimeError? -- nosy: +kaizhu

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

Daniel Diniz <[EMAIL PROTECTED]> added the comment: Antoine, All the cases I could find would be more "test" than "use" cases. Given that most ways to abort I find in 3.0 are related to "undetected error"s in trunk, I'm almost convinced that 3.0 is right here :) My last worry is that it'd be kin

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > Except that it wasn't an infinite loop in 2.5 and isn't in trunk: it > terminates on overflower's except. That's because the stated behaviour is only implemented in 3.0 and not in 2.x. I'm not sure what motivated it, but you are the first o

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

Daniel Diniz <[EMAIL PROTECTED]> added the comment: Antoine, Thanks for your analysis. I still believe this is a regression for the case described, but take my opinion with a grain of salt :) >> looking at the code for _Py_CheckRecursiveCall(), I don't think it >> is a bug but a feature. It d

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: I'm no expert in recursion checking inside the Python interpreter, but looking at the code for _Py_CheckRecursiveCall(), I don't think it is a bug but a feature. Here how I understand it. When the recursion level exceeds the normal recursion

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

Changes by Guido van Rossum <[EMAIL PROTECTED]>: -- nosy: +gvanrossum ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

New submission from Daniel Diniz <[EMAIL PROTECTED]>: The following code works[1] on trunk and 2.5.1, but crashes with "Fatal Python error: Cannot recover from stack overflow," on py3k as of rev65676: ## # Python 3.0b2+ (py3k:65676, Aug 14 2008, 14:37:38) # [GCC 4.1.3 20070929 (prerelease) (