From b046a247ae0220a415b085930992dae046d4439f Mon Sep 17 00:00:00 2001 From: Steven Schubiger Date: Tue, 4 Oct 2016 17:32:46 +0200 Subject: Mention running tests through valgrind in README --- README | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README b/README index afd40b9..5890e6d 100644 --- a/README +++ b/README @@ -20,6 +20,7 @@ Requirements gcc make perl +valgrind (optional) Build instructions ------------------ @@ -39,6 +40,12 @@ debugging output by issuing `make FLAGS=-DDEBUG'. The intention is to provide some memory allocation diagnostics (and might be extended in future). Usually, a debugging build is not required. +Furthermore, tests can be run through valgrind by issuing, for +example, `make check_valgrind 2>&1 | tee valgrind.out'. The +file provided here for the `tee' invocation will be populated +with the captured output from both standard output and error +stream. + Documentation ------------- See man page source file: colorize.1. -- cgit v1.2.3