Tim Peters <tim.one@comcast.net> writes: > After digesting some ideas from David Abrahams offlist, I believe I may have > a much simpler way to make a bulletproof "is or isn't this address from a > pymalloc pool?" test. Described as a diff from current pymalloc: 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 :-). For the architectures we care about, this seems to be guaranteed; on other architectures, people will need to disable pymalloc. Regards, Martin
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