LI-14190 - Looking for best memory leak procedure for linux
Posted on 2010-11-19
We are using gcc --version 22.214.171.12480704 (Red Hat 4.1.2-48). We have memory leaks that rival the water supply lines in Boston.
We have considered making our own "new" and "delete" wrapper functions to track where this is happening, but prefer to use gdb/sdb or something else already written that would let us discover where we are not deleting objects, etc. We are only somewhat familiar with gdb/sdb, but willing to try anything.
Anyone have suggestions/sites we can go to, to find a good procedure for finding these leaks?