Merged revisions 111606 via svnmerge from

https://origsvn.digium.com/svn/asterisk/trunk

................
r111606 | tilghman | 2008-03-28 09:37:28 -0500 (Fri, 28 Mar 2008) | 11 lines

Merged revisions 111605 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r111605 | tilghman | 2008-03-28 09:35:45 -0500 (Fri, 28 Mar 2008) | 3 lines

Update debugging text, since Valgrind eliminated the --log-file-exactly option.
(Closes issue #12320)

........

................


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.0@111607 65c4cc65-6c06-0410-ace0-fbb531ad65f3

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.