[martin@v.loewis.de]
> This sounds quite good. The only flaw is that you need to trust that
> the machine has paged memory - otherwise, rounding down an arbitrary
> address to a 4k boundary, and then reading a value may cause an access
> violation (or may, say, fetch data from some peripheral device, thus
> starting the coffee machine :-).
pymalloc always relied on that assumption, so that part isn't new.
> For the architectures we care about, this seems to be guaranteed; on
> other architectures, people will need to disable pymalloc.
Either that or buy a reasonable machine <wink>. A fair number of people
have tried pymalloc by now, and nobody has reported a problem. I suppose
they may have been lucky, and that feeding PyMem_{FREE, Free, DEL, Del} into
PyMalloc_Free too may greatly strain their luck if so.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4