Issue 31347: possible undefined behavior in _PyObject_FastCall_Prepend - Python tracker

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: benjamin.peterson
Priority: normal Keywords:

Created on 2017-09-04 23:32 by benjamin.peterson, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 3329 merged benjamin.peterson, 2017-09-04 23:35
Messages (2)
msg301283 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2017-09-04 23:32
As seen by ubsan:
../cpython/Objects/call.c:858:9: runtime error: null pointer passed as argument 2, which is declared to never be null
msg301298 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2017-09-05 05:23
New changeset a3070d530c70477273cacbc61660b318582fff44 by Benjamin Peterson in branch 'master':
bpo-31347: _PyObject_FastCall_Prepend: do not call memcpy if args might not be null (#3329)
https://github.com/python/cpython/commit/a3070d530c70477273cacbc61660b318582fff44