[issue8020] Crash in Py_ADDRESS_IN_RANGE macro

[Tim Peters]

Tim Peters <tim.peters at gmail.com> added the comment:

Amaury, I have no real idea what your "No, the description above says it: ..." is a response to, but if it's to my point that obmalloc is not intended to be thread-safe, it's not addressing that point.  Any case in which another thread can affect a thread currently running in obmalloc is forbidden:  forbidden, not allowed, begging for undefined behavior, etc etc.

> Could we use an "inline" function instead of a macro?

If every C compiler on every platform Python runs on supports such a thing with exactly the same spelling, sure ;-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8020>
_______________________________________