|
From: Philippe W. <phi...@sk...> - 2016-10-06 20:36:49
|
On Thu, 2016-10-06 at 21:59 +0200, Philippe Waroquiers wrote: > But of course, when calling VALGRIND_MEMPOOL_FREE, by definition, the > addr > given as argument is supposed to be a chunk of the pool, and is > released. > So, this flag is by itself useless, unless it is combined with > VALGRIND_MEMPOOL_METAPOOL. I just confirmed using the test leak-autofreepool 3 that if you do a leak search before you have cleaned up the pool, then you get again an internal assertion in valgrind due to overlapping blocks. So, effectively, using only the flag VALGRIND_MEMPOOL_AUTO_FREE is not very useful, as any leak search done with such a not released pool will crash. Philippe |