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 serhiy.storchaka
Recipients ammar2, cstratak, hroncok, methane, pablogsal, serhiy.storchaka, vstinner
Date 2019-12-06.08:48:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1575622119.91.0.597911963065.issue38980@roundup.psfhosted.org>
In-reply-to
Content
In case of malloc, every memory allocating code need to use malloc/calloc/realloc. This is official and the only way to allocate a memory. But we do not guarantee that Python core uses only public C API like PyErr_Occurred(). It can use more low-level and efficient but less safer C API internally. It can replace the function with a macro which access internal structures directly (for compiling the core only). And this is actually the case. Overridding the public C API functions not always has an effect on the core.

So I think that adding -fno-semantic-interposition will likely not break many things which were not broken before.

But this should be discussed on Python-Dev. I am sure some C API functions are purposed to be overridden.
History
Date User Action Args
2019-12-06 08:48:40serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, methane, cstratak, ammar2, hroncok, pablogsal
2019-12-06 08:48:39serhiy.storchakasetmessageid: <1575622119.91.0.597911963065.issue38980@roundup.psfhosted.org>
2019-12-06 08:48:39serhiy.storchakalinkissue38980 messages
2019-12-06 08:48:39serhiy.storchakacreate