Fredrik Lundh fredrik at pythonware.com
Mon Aug 30 19:36:27 CEST 2004

• Previous message: [Python-Dev] python vs. valgrind
• Next message: [Python-Dev] Re: python vs. valgrind
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> most (all?) errors occur in PyObject_Free and PyObject_Realloc, which indicates
> that the problem is either in pymalloc or valgrind itself (and in my experience, while
> vladimir and tim almost never mess up, valgrind is *never* wrong...)

on the other hand:

http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Objects/obmalloc.c?r1=2.51&r2=2.52

(but I must be tired; can anyone explain how "making the function last"
prevents the code from looking at uninitialized data?)

</F> 

---

• Previous message: [Python-Dev] python vs. valgrind
• Next message: [Python-Dev] Re: python vs. valgrind
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list