2 ms·

The "#ifdef DEBUG..." option is pretty much exactly what they did: http://lists.gnu.org/archive/html/coreutils/2014-08/txtVTwv5erR5o.txt http://lists.gnu.org/a

• khc 12y ago
  The proper thing to do is include valgrind.h and use the macros to determine if it's running under valgrind. Alternatively to accommodate other tools, hide it behind an env var. We should make it as easy to test production binaries as possible.