Michael Hudson wrote: > > Neal Norwitz <neal@metaslash.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 > > http://sourceforge.net/tracker/?func=detail&atid=105470&aid=495401&group_id=5470 > > ? > > 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 bug-tracker) ?! -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
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