21 Aug
2012
21 Aug
'12
6:24 p.m.
On Tue, Aug 21, 2012 at 10:32 AM, Claude
Your mail does not contain any relevant text.
I do not understand what you tell me...
In email, your valgrind output does not show up. Perhaps because it is not plain text? Everything shows up fine in the web thread. FWIW, assuming release_memory() should call delete[] on the pool's internal memory buffers, this does indeed seem like a leak. Moreover, it appears that delete[] is never called, even at pool destruction. Valgrind actually rarely spews spurious errors. Sometimes they don't matter (invalid reads/writes for memcpy on structures with padding, etc...), but it's pretty much always spot-on. Brian