[Python-Dev] Mixing memory management APIs
Wed, 06 Feb 2002 17:49:24 +0100
Michael Hudson wrote:
> Neal Norwitz <email@example.com> writes:
> > Because of Michael Hudson's request, I tried running Purify
> > --with-pymalloc enabled. The results were a bit surprising: 13664 errors!
> > All the errors were in unicodeobject.c. There were 3 types of errors:
> > Free Memory Reads, Array Bounds Reads, and Unitialized Memory Reads.
> > The line #s were in strange places (e.g., in a function declaration
> > and accessing self->length in an if clause, after it was accessed w/o error).
> > The line #s are primarily: unicodeobject.c:2875, and unicodeobject.c:2214.
> Might this have something to do with
> bug [ #495401 ] Build troubles: --with-pymalloc
> Is there a reason one of the fixes for this problem hasn't been
> checked in yet?
It is currently assigned to Martin.
Perhaps I should just take the Unicode patch and check it in (the
first one, not the second one for the reasons stated in the
CEO eGenix.com Software GmbH
Company & Consulting: http://www.egenix.com/
Python Software: http://www.egenix.com/files/python/