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.

Author gregory.p.smith
Recipients Mark.Shannon, gregory.p.smith
Date 2019-06-03.04:16:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The undefined behavior sanitizer buildbot is flagging a bunch of issues in master (3.8) of late:

AssertionError: 'Objects/classobject.c:74:29: runtime erro[139 chars]re\n' != ''
- Objects/classobject.c:74:29: runtime error: null pointer passed as argument 2, which is declared to never be null
- /usr/include/string.h:43:28: note: nonnull attribute specified here


This appears to be coming from a relatively new classobject.c:method_vectorcall() function

method_vectorcall(PyObject *method, PyObject *const *args,
                  size_t nargsf, PyObject *kwnames)

Which looks like it is probably being called with NULL args value and thus winds up calling memcpy() with src=NULL.

This was introduced in for the PEP 590 implementation.
Date User Action Args
2019-06-03 04:16:10gregory.p.smithsetrecipients: + gregory.p.smith, Mark.Shannon
2019-06-03 04:16:10gregory.p.smithsetmessageid: <>
2019-06-03 04:16:10gregory.p.smithlinkissue37138 messages
2019-06-03 04:16:10gregory.p.smithcreate