diff --git a/runtime/doc/debug.txt b/runtime/doc/debug.txt
index 5593902..eb5a305 100644
--- a/runtime/doc/debug.txt
+++ b/runtime/doc/debug.txt
@@ -39,7 +39,7 @@
 
 ==============================================================================
 
-2. Locating memory leaks				*debug-leaks*
+2. Locating memory leaks			*debug-leaks* *valgrind*
 
 If you suspect Vim is leaking memory and you are using Linux, the valgrind
 tool is very useful to pinpoint memory leaks.
@@ -47,14 +47,18 @@
 First of all, build Vim with EXITFREE defined.  Search for this in MAKEFILE
 and uncomment the line.
 
-Use this command to start Vim:				*valgrind*
+Use this command to start Vim:
 >
-	valgrind --log-file=valgrind.log ./vim
+	valgrind --log-file=valgrind.log --leak-check=full ./vim
 
 Note: Vim will run much slower.  If your .vimrc is big or you have several
 plugins you need to be patient for startup, or run with the "-u NONE"
 argument.
 
+There are often a few leaks from libraries, such as getpwuid() and
+XtVaAppCreateShell().  Those are unavoidable.  The number of bytes should be
+very small a Kbyte or less.
+
 ==============================================================================
 
 3. Windows Bug Reporting				*debug-win32*