[asterisk-commits] tilghman: branch 1.4 r88116 - /branches/1.4/doc/valgrind.txt

[SVN commits to the Asterisk project]

Author: tilghman
Date: Thu Nov  1 12:17:56 2007
New Revision: 88116

URL: http://svn.digium.com/view/asterisk?view=rev&rev=88116
Log:
Add some notes on using valgrind

Added:
    branches/1.4/doc/valgrind.txt   (with props)

Added: branches/1.4/doc/valgrind.txt
URL: http://svn.digium.com/view/asterisk/branches/1.4/doc/valgrind.txt?view=auto&rev=88116
==============================================================================
--- branches/1.4/doc/valgrind.txt (added)
+++ branches/1.4/doc/valgrind.txt Thu Nov  1 12:17:56 2007
@@ -1,0 +1,19 @@
+If you're having certain types of crashes, such as those associated with
+memory corruption, a bug marshal may ask you to run Asterisk under valgrind.
+You should follow these steps, to give the bug marshal the maximum amount
+of information about the crash.
+
+1.  Run 'make menuselect' and in the Compiler Options, enable MALLOC_DEBUG
+	and DONT_OPTIMIZE.  A bug marshal may also ask you to enable additional
+	compiler flags, such as DEBUG_THREADS, depending upon the nature of the
+	issue.
+
+2.  Rebuild and install Asterisk.
+
+3.  Run Asterisk as follows:
+	valgrind --log-file-exact=valgrind.txt asterisk -vvvvcg 2>malloc_debug.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.
+

Propchange: branches/1.4/doc/valgrind.txt
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: branches/1.4/doc/valgrind.txt
------------------------------------------------------------------------------
    svn:keywords = Id Author Keywords Revision

Propchange: branches/1.4/doc/valgrind.txt
------------------------------------------------------------------------------
    svn:mime-type = text/plain