|
From: Philippe W. <phi...@so...> - 2017-08-15 21:37:43
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=477ef25e67b1a5b769d6704f29bbecabbe9363dc commit 477ef25e67b1a5b769d6704f29bbecabbe9363dc Author: Philippe Waroquiers <phi...@sk...> Date: Tue Aug 15 23:30:46 2017 +0200 Small improvement to user manual: capitalise another occurence of memcheck (yes, I am experimenting with valgrind git repository :) Diff: --- docs/xml/manual-core.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml index c88bffe..4cd26a5 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -1728,7 +1728,7 @@ Massif, Helgrind, DRD), the following options apply.</para> For massif and helgrind, specifying <varname>full</varname> implies to capture a stack trace for each free operation, while normally these tools only capture an allocation stack - trace. For memcheck, the cpu overhead for the + trace. For Memcheck, the cpu overhead for the value <varname>full</varname> is small, as this can only be used in combination with <option>--keep-stacktraces=alloc-and-free</option> or |