Experimental Physics and
Industrial Control System

Michael Davidsaver <[email protected]> · Mon, 06 Apr 2015 11:30:29 -0400

On 04/06/2015 11:22 AM, Andrew Johnson wrote:
...
> * Which version of the header we would include? On RHEL 6.6 I have
> valgrind-3.8.1 installed, but I see the latest release is 3.10.1; does
> the include file need to match the valgrind version? I assume not given
> their instructions for it, but is it guaranteed to be both backwards and
> forwards-compatible? Major version only? My version doesn't have 64-bit
> Windows support but does have 32-bit MS, Cygwin and MinGW.

I'll investigate.

As a fallback, how about "epicsValgrind.h" with a NVALGRIND-like
disabling macro?

> * Would we normally define NVALGRIND, so you'd have to explicitly turn
> it on for debugging (maybe in our debug builds), or not and leave the
> full macros in always?

I'm inclined to enable it by default for all targets.  The overhead is
small and would only appear in code paths which do allocation.

> Anyone else want to comment on this idea?

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System