GH-123185: Check for NULL after calling _PyEvalFramePushAndInit (GH-123194)
This commit is contained in:
6
Python/executor_cases.c.h
generated
6
Python/executor_cases.c.h
generated
@@ -4152,9 +4152,13 @@
|
||||
args[-1] = self;
|
||||
init_frame = _PyEvalFramePushAndInit(
|
||||
tstate, init_func, NULL, args-1, oparg+1, NULL, shim);
|
||||
frame->return_offset = 1 + INLINE_CACHE_ENTRIES_CALL;
|
||||
stack_pointer += -2 - oparg;
|
||||
assert(WITHIN_STACK_BOUNDS());
|
||||
if (init_frame == NULL) {
|
||||
_PyEval_FrameClearAndPop(tstate, shim);
|
||||
JUMP_TO_ERROR();
|
||||
}
|
||||
frame->return_offset = 1 + INLINE_CACHE_ENTRIES_CALL;
|
||||
/* Account for pushing the extra frame.
|
||||
* We don't check recursion depth here,
|
||||
* as it will be checked after start_frame */
|
||||
|
||||
Reference in New Issue
Block a user