[Python-Dev] Python under valgrind

"Martin v. Löwis" martin at v.loewis.de
Fri Nov 28 20:03:01 CET 2008

> I suppose valgrind could be confused by PyFree's pool address validation
> that intentionally reads the memory just before the allocated block, and
> incorrectly attributes it to a previously allocated (and hence freed)
> block, but I can't prove that. 

I agree this is the likely cause. To prove it, you will need to find
the line number associated with 0x808EBDF. Either you available debug
information, or disassemble PyObject_Free to determine what specific
read operation is causing the report. Most likely, you find it is
inside Py_ADDRESS_IN_RANGE, in the attempt to read pool->arenaindex.


More information about the Python-Dev mailing list