Hrvoje Niksic wrote: > A friend pointed out that running python under valgrind (simply "valgrind > python") produces a lot of "invalid read" errors. Reading up on > Misc/README.valgrind only seems to describe why "uninitialized reads" should > occur, not invalid ones. For example: [...] > 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. Has anyone investigated this kind of valgrind > report?
Did you use the suppressions file as suggested in Misc/README.valgrind? --suppressions=Misc/valgrind-python.supp -- Amaury Forgeot d'Arc _______________________________________________ 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
