Subject: Re: [boost] Review of a safer memory management approach for C++
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2010-06-07 17:22:39
07/06/2010 18:14, Roland Bock wrote:
> Writing you own allocator and then suddenly not being able to use
> valgrind anymore, that's the memory fun today.
It's pretty easy to add hooks for valgrind to work properly with your
own allocator, or even your own thread library.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk