X-Git-Url: http://git.asterisk.org/gitweb/?p=asterisk%2Fasterisk.git;a=blobdiff_plain;f=doc%2Fvalgrind.txt;h=4b89eec9c4ff17c456db4b27d2929d7c27e31cba;hp=1ac4b2bd7688295620a75b09edc824c39cdda95d;hb=3f78a375a002758ddb9e16293aef90472f3075e4;hpb=cafce80cd52ada3e9e64935c8b015f98231cef00

diff --git a/doc/valgrind.txt b/doc/valgrind.txt
index 1ac4b2b..4b89eec 100644
--- a/doc/valgrind.txt
+++ b/doc/valgrind.txt
@@ -13,7 +13,14 @@ of information about the crash.
 3.  Run Asterisk as follows:
 	valgrind --log-file-exactly=valgrind.txt asterisk -vvvvcg 2>malloc_debug.txt
 
+	UPDATE:  The newest version of valgrind has eliminated the
+	--log-file-exactly option.  If you are running valgrind 3.3.0 or higher,
+	just use the --log-file option, keeping in mind that Valgrind will append
+	a trailing suffix onto valgrind.txt.
+
 4.  Reproduce the issue.  Following the manifestation of the issue (or when
 	the process crashes), upload the two files, valgrind.txt and
-	malloc_debug.txt to the issue tracker.
+	malloc_debug.txt to the issue tracker.  If you are using the --log-file
+	option, note that valgrind.txt will have a trailing suffix.  That's fine,
+	just upload that file.