Hi Bruce, > > The ability to check against memory leaks is an important feature > > in the test suite, and it warrants jumping through a number of hoops. > > Perhaps then it is worth testing more directly by replacing the > memory management calls in the memory leak tests?
If we want to check whether a library function, such as dprintf(), has a memory leak in this way, we need to override the system's malloc() implementation. But this is only possible a) on ELF systems, or b) when linking statically. Which brings portability / build constraints for the tests, which I would better avoid. Bruno
