Well, you can run your tests under something like valgrind and it will tell
you.
Now which test leaked?
Pretty easy to find out. Valgrind gives us the call-stack of the allocation that leaked, and most code is only executed by a few tests. (Google "microtest" to see why (and "Mike Wrote Tests").)
Some people make the test-runners keep track of memory usage, and it complains about specific tests.
Use code-review and/or pair programming, and sensible coding standards, to make sure other kinds of resources are not leaked.
C. Keith Ray
MARKETPLACE
Switch to: Text-Only, Daily Digest ? Unsubscribe ? Terms of
[Non-text portions of this message have been removed]
