[issue35269] A possible segfault involving a newly-created coroutine

Andrew Svetlov added the comment: Thanks, Zackery! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35269] A possible segfault involving a newly-created coroutine

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35269] A possible segfault involving a newly-created coroutine

miss-islington added the comment: New changeset ae02a929ddd748b67b3e6f6c6665267f031142e7 by Miss Islington (bot) in branch '3.7': bpo-35269: Fix a possible segfault involving a newly-created coroutine (GH-10585)

[issue35269] A possible segfault involving a newly-created coroutine

Change by miss-islington : -- pull_requests: +9836 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35269] A possible segfault involving a newly-created coroutine

miss-islington added the comment: New changeset 062a57bf4b768ef726975bcc1d34398387520147 by Miss Islington (bot) (Zackery Spytz) in branch 'master': bpo-35269: Fix a possible segfault involving a newly-created coroutine (GH-10585)

[issue35269] A possible segfault involving a newly-created coroutine

Change by Yury Selivanov : -- nosy: +njs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35269] A possible segfault involving a newly-created coroutine

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9829 stage: -> patch review ___ Python tracker ___ ___

[issue35269] A possible segfault involving a newly-created coroutine

New submission from Zackery Spytz : If compute_cr_origin() fails in PyCoro_New(), coro->cr_origin won't be initialized. This will cause a crash during the coroutine's deallocation. I'll create a PR for this issue. -- components: Interpreter Core, asyncio messages: 330031 nosy: