X-Git-Url: https://git.cinelerra-gg.org/git/?a=blobdiff_plain;f=parts%2FDeveloper.tex;h=8f8cab221a08a81c7904e8f9a08751e9d32c1e6c;hb=6bb9bb301c01bcf89083f1c9859724e0125c248a;hp=ca0889edcf695bd38474a79cebb705c6db48eec7;hpb=57a10c712aed39a74039379695c7f4f14015827a;p=goodguy%2Fcin-manual-latex.git

diff --git a/parts/Developer.tex b/parts/Developer.tex
index ca0889e..8f8cab2 100644
--- a/parts/Developer.tex
+++ b/parts/Developer.tex
@@ -520,6 +520,10 @@ It is impossible to test everything with valgrind because some things are just t
 deadly. The listing of the memory leaks can be quite voluminous so locating the \textit{LEAK SUMMARY} section
 towards the end of the report is most useful.
 
+Another very useful valgrind run to locate unitialized variables while executing is:
+
+\hspace{2em}\texttt{valgrind -{}-log-file=/tmp/log -{}-tool=memcheck\\
+	-{}-num-callers=32 ./ci}
 
 \section{CFLAGS has -Wall}
 \label{sec:cflags_has_-wall}