I was wondering if you can test memory leaking at all. We have used Rational Purify to generate a report after step through the code. Memory were leak randomly, so we caught memory only randomly. Any other better tools or strategies can be used?
How many ways can I break your code
IBM Certified Database Administrator
Sun Certified Java Programmer
Oracle Certified Associate
Tools like BoundsChecker or Purify use the same technique to arrive at their goals.
These are runtime leak identification tools.
This they achieve by instrumenting the object code with their own headers - guard bytes. During a test run, pointers to allocated memory are tracked. Finally, at the end of the run, the consolidation takes place and the report gets produced.
Apparently, this technique can only cover those areas of the code which were exercised during a run. As such, the tool is as effective as the test case that you run.
Perhaps you are looking at a static analysis tool. PC Lint is a tool in that category.
["Carpe diem, quam minimum credula postero!" -Horace]