[Martin v. Loewis]
> ...
> Now, the question is: where does that pointer come from? This should
> be from funcobject.c:457, which says
>
> k = PyMem_NEW(PyObject *, 2*nk);
>
> Unless I'm mistaken, this expands to malloc().
Which version of Python is getting built here?
In 2.3, PyMem_NEW resolves to malloc() in a release build, but not a debug
build (in a debug build, all Python memory API calls go through pymalloc).
This may be vaguely <wink> relevant, since Marc said
This doesn't happen if either --without-pymalloc or --with-pydebug
is given.
In the former case (--without-pymalloc) pymalloc isn't used at all; in the
latter case (--with-pydebug) pymalloc is always used. In 2.3. Since I saw
a
/opt/local/python/lib/python2.3/config/install-sh
^^^^^^^^^
flash by, I figure that's right for this build.
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