|
From: Anupam P. <anu...@gm...> - 2012-04-06 20:01:29
|
In one of my memory managers I let clients allocate memory of a given size but I do not provide a way to free it. This memory should exist throughout the lifetime of my program and I simply free my memory banks at the end of my program. The clients do not need to call explicit free on for these allocations. I register allocation using VALGRIND_MEMPOOL_ALLOC() as I want other checks like (out of bound read/write) to be done by valgrind. Is there a way to tell valgrind to not check for leaks for this memory manager ? Anupam |