|
From: Nicholas N. <nj...@so...> - 2019-04-08 00:21:43
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=b71265fbc9e65936a46158ffb85a5242efbb741e commit b71265fbc9e65936a46158ffb85a5242efbb741e Author: Nicholas Nethercote <nne...@mo...> Date: Mon Apr 8 10:18:38 2019 +1000 Mention --num-callers more in DHAT docs. Diff: --- dhat/docs/dh-manual.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index 56f5b6a..da71720 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -67,7 +67,9 @@ Valgrind use, you probably do want to turn optimisation on, since you should profile your program as it will be normally run.</para> <para>Second, you need to run your program under DHAT to gather the profiling -information.</para> +information. You might need to reduce the <option>--num-callers</option> value +to get reasonably-sized output files, especially if you are profiling a large +program; some trial and error might be needed to find a good value.</para> <para>Finally, you need to use DHAT's viewer (in a web browser) to get a detailed presentation of that information.</para> @@ -146,6 +148,10 @@ built with full debugging information.</para> <computeroutput>dh_view.html</computeroutput>. Use the "Load" button to choose a DHAT output file to view.</para> +<para>If loading takes a long time, it might be worth re-running DHAT with a +smaller <option>--num-callers</option> value to reduce the stack depths, +because this can significantly reduce the size of DHAT's output files.</para> + <sect2><title>The Output Header</title> |