Re: [Boost-users] [Test] How to treat memory leaks as errors?

Subject: Re: [Boost-users] [Test] How to treat memory leaks as errors?
From: OvermindDL1 (overminddl1_at_[hidden])
Date: 2009-09-27 03:45:31

On Sun, Sep 27, 2009 at 1:37 AM, OvermindDL1 <overminddl1_at_[hidden]> wrote:
> On Sun, Sep 27, 2009 at 12:01 AM, Gennadiy Rozental <rogeeff_at_[hidden]> wrote:
>> OvermindDL1 wrote:
>>>
>>> For note, the google memory tracker allows you to even partition
>>> segments of your program off, letting you test for memory leaks just
>>> from those sections and so forth, it is very powerful, as well as
>>> multi-platform.
>>
>> Can you point to docs/download location? How portable is it? At what point
>> it performs instrumentation?
>
> Main site: Â http://goog-perftools.sourceforge.net/
>
> The memory allocator and leak checker is very portable as I recall,
> the profiler is not as portable (but you do not need it from the
> sounds of it), but they are working on it.
> This is what Google actually uses in their own products and servers,
> very well tested.
>
> It will report results either at program end, or at any specific time
> you specify, as stated, it is very powerful, and very easy to use, I
> have been quite happy with it, and the memory allocator has speed up
> some of my memory intensive programs by a surprising amount.
>
> The code is actually very generic, it could actually, quite easily,
> become a boost library (if Google would ever offer it up as such),
> maybe with some namespace changes and such though.
>

Correction, now located here:  http://code.google.com/p/google-perftools/