On 11/7/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > Neal Norwitz schrieb: > > at 0x44FA06: Py_ADDRESS_IN_RANGE (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 > > PyType_Ready. I'll file a bug report with valgrind to help determine > > if this is a problem in Python or valgrind. > > http://bugs.kde.org/show_bug.cgi?id=136989 > > As Tim explains, a read from Py_ADDRESS_IN_RANGE 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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
