On Wed, 20 Jun 2001, Andrew Dunbar wrote:
> > Actually, coming to think of it, me (or anyone alse with access to it)
> > running Purify on the code should probably be part of the release
> > procedure! What do you think?
>
> I'm all for it but can anybody recommend some good *free* memory leak
> tools for Windows and our other platforms. Then I can get to work on
> it myself (:
Owen Taylor's memprof is nice, but I don't know how much
it likes C++. It shouldn't be too far off if your default
new uses malloc.
I think it's i386-linux-glibc-elf-only, tho'.
Matthew.
