[issue1595] Probable extra semicolon in Py_LeaveRecursiveCall macro

Martin v. Löwis added the comment: Thanks again for pointing that out. Fixed in r60750. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ __

[issue1595] Probable extra semicolon in Py_LeaveRecursiveCall macro

Changes by Georgij Kondratjev: -- nosy: +orivej __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1595] Probable extra semicolon in Py_LeaveRecursiveCall macro

Changes by Christian Heimes: -- priority: -> high __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue1595] Probable extra semicolon in Py_LeaveRecursiveCall macro

Martin v. Löwis added the comment: I think you are right - that's a bug. As a consequence, overflowed would be cleared less often than it is now, which in turn may cause a fatal abort in case it fails to recover from a stack overflow (i.e. if it consumes another 50 stack frames, instead of unwind

[issue1595] Probable extra semicolon in Py_LeaveRecursiveCall macro

New submission from Amaury Forgeot d'Arc: In file ceval.h, the macro Py_LeaveRecursiveCall is defined like this: #define Py_LeaveRecursiveCall() \ do{ if((--PyThreadState_GET()->recursion_depth) < \ _Py_CheckRecursionLimit - 50); \