[Python-Dev] valgrind (original) (raw)

Neal Norwitz nnorwitz at gmail.com
Wed Nov 8 07:04:10 CET 2006

On 11/7/06, "Martin v. Löwis" <martin at v.loewis.de> wrote:

Neal Norwitz schrieb: > at 0x44FA06: PyADDRESSINRANGE (obmalloc.c:1741) > > Note that the free is inside qsort. The memory freed under qsort > should definitely not be the bases which we allocated under > PyTypeReady. I'll file a bug report with valgrind to help determine > if this is a problem in Python or valgrind. > http://bugs.kde.org/showbug.cgi?id=136989

As Tim explains, a read from PyADDRESSINRANGE is fine, and by design. If p is the pointer, we do

Yeah, thanks for going over it again. I was tired and only half paying attention last night. Tonight isn't going much better. :-( I wonder if we can capture any of these exchanges and put into README.valgrind. I'm not about to do it tonight though.

n

More information about the Python-Dev mailing list