[Python-Dev] Debug entry points for PyMalloc

[Fredrik Lundh]

guido wrote:


> > We have one already:  turn off pymalloc.  How useful has, e.g., the =
debug
> > Linux malloc been for you in finding memory problems?
>=20
> The only one I've used is electric fence.  It's slow as a pig, but
> catches virtually all bad writes at the point of writing.  I've used
> it with great success once or twice (during the early stages of
> developing new-style classes I wrote a lot of rough C code).

I've played a little with this one:

    http://developer.kde.org/~sewardj/

which complained about accesses to uninitialized data down
in the tokenizer module in 2.2.1c1.  (still haven't figured out
exactly where/why, though).

</F>