A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2006-March/062847.html below:

[Python-Dev] Prevalence of low-level memory abuse?

[Python-Dev] Prevalence of low-level memory abuse? [Python-Dev] Prevalence of low-level memory abuse?Edward Loper edloper at gradient.cis.upenn.edu
Mon Mar 27 01:47:31 CEST 2006
Tim Peters wrote:
>     If extension modules in real life prove as sloppy as Python's
>     front end, we'll have to revert the objimpl.h + pymem.h part of this
>     patch.  Note that no problems will show up in a debug build (all
>     calls still go thru obmalloc then).  Problems will show up only in a
>     release build, most likely segfaults.

Could the debug build's macros for PyMem/PyObject_new/free be modified 
to check for mismatches?  Or would storing information about which 
method was used to allocate each pointer be too expensive?  Perhaps a 
special build could be used to check for mismatches?

-Edward
More information about the Python-Dev mailing list

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