Tim Peters <tim.one@comcast.net> writes:
> I think you have to under this scheme, although I'm not clear on what "the
> problem" is you're trying to solve. I'm trying to cater to allocating via
> PyMem_{MALLOC, Malloc} then free'ing via _PyMalloc_Free.
Is *that* the motivation? I thought you were trying to accommodate
your killer.py where Python code can trick pymalloc into believing
that it owned the memory which it actually had allocated by forwarding
to system malloc (see the subject).
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