Re: include valgrind.h in Base?

[Michael Davidsaver <mdavidsaver@bnl.gov>]

On 04/06/2015 01:37 PM, J. Lewis Muir wrote:
> ...
> I'm not experienced with Valgrind

I'd invite you to try it.  It's an *extremely* useful tool for finding
memory allocation an access problems.

It also has a companion tool helgrind which looks at threading and locking.

> ...
> Is it because the code uses memory pools and hence is not allocating and
> deallocating memory "normally?"

This is the purpose.

>  If so, what about instead modifying the
> code to support a way to easily disable the use of memory pools?

There are already compile time conditions to do this (which I've been
using).  If you're talking about runtime conditions, this is of course
doable.  Patches welcomed :)

> Then
> you could run the program under Valgrind with memory pools disabled, and
> there wouldn't be a need for any Valgrind-specific modifications to the
> code?

I'd like both options if I could have them.  I just think the valgrind
instrumentation is more useful.