Issue 31347: possible undefined behavior in _PyObject_FastCall

The Wayback Machine - https://web.archive.org/web/20210523034057/https://bugs.python.org/issue31347

Issue31347

classification

Title:	possible undefined behavior in _PyObject_FastCall_Prepend
Type:		Stage:	resolved
Components:		Versions:	Python 3.7, Python 3.6

process

Created on 2017-09-04 23:32 by benjamin.peterson, last changed 2017-09-05 05:25 by benjamin.peterson. 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) *	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) *	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

History
Date	User	Action	Args
2017-09-05 05:25:55	benjamin.peterson	set	status: open -> closed resolution: fixed stage: resolved
2017-09-05 05:23:44	benjamin.peterson	set	messages: + msg301298
2017-09-04 23:35:49	benjamin.peterson	set	pull_requests: + pull_request3351
2017-09-04 23:32:36	benjamin.peterson	create

Issue 31347: possible undefined behavior in _PyObject_FastCall_Prepend