diff options
authortilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b>2008-03-28 14:35:45 +0000
committertilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b>2008-03-28 14:35:45 +0000
commit3bbdc8e06c23f62842b31d2b190c8ac9dd2d0c92 (patch)
parentbb5aaa7d75848b347d77bca081a9dd6130fe415e (diff)
Update debugging text, since Valgrind eliminated the --log-file-exactly option.
(Closes issue #12320) git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@111605 f38db490-d61c-443f-a65b-d21fe96a405b
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/valgrind.txt b/doc/valgrind.txt
index 1ac4b2bd7..4b89eec9c 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.