Wed Dec 10 18:03:00 GMT 2003
>How can I do this on an easy way?
The easiest way to do it is to test for memory leaks in a test (non-production) environment.
In that way, you can instrument the code any way that you find appropriate.
You can even replace the memory manager with one of your own devising. Or some third-party memory manager, that has facility for tracking memory leaks. Such as the ones from <http://www.rational.com/>, the IBM Rational Suite (Purify, Quantify, et al).
Test early. Test often.
More information about the Gcc-help