From: Tilghman Lesher Date: Thu, 1 Nov 2007 17:17:56 +0000 (+0000) Subject: Add some notes on using valgrind X-Git-Tag: 1.4.14~71 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9c6615d58556a959cceaa335adab3b9836c9a672;p=thirdparty%2Fasterisk.git Add some notes on using valgrind git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@88116 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/doc/valgrind.txt b/doc/valgrind.txt new file mode 100644 index 0000000000..067e29618a --- /dev/null +++ b/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-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. +