From f8247040e6231c4b3b5099ea3a526348b7941566 Mon Sep 17 00:00:00 2001 From: russell Date: Sat, 19 Jan 2008 00:19:29 +0000 Subject: Creating tag for the release of asterisk-1.6.0-beta1 git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.6.0-beta1@99163 f38db490-d61c-443f-a65b-d21fe96a405b --- trunk/doc/valgrind.txt | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 trunk/doc/valgrind.txt (limited to 'trunk/doc/valgrind.txt') diff --git a/trunk/doc/valgrind.txt b/trunk/doc/valgrind.txt new file mode 100644 index 000000000..1ac4b2bd7 --- /dev/null +++ b/trunk/doc/valgrind.txt @@ -0,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-exactly=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. + -- cgit v1.2.3