b544c53778
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r225484 | lmadsen | 2009-10-22 16:51:52 -0500 (Thu, 22 Oct 2009) | 11 lines Clean valgrind output by suppressing false errors. Update valgrind.txt documentation and add valgrind.supp file in order to allow those who are creating valgrind output to have less false errors in the logfile. (closes issue #16007) Reported by: atis Patches: valgrind.txt.diff uploaded by atis (license 242) asterisk2.supp uploaded by atis (license 242) Tested by: atis, amorsen ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@225485 65c4cc65-6c06-0410-ace0-fbb531ad65f3
25 lines
1 KiB
Text
25 lines
1 KiB
Text
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 --suppressions=/usr/src/asterisk/contrib/valgrind.supp --log-fd=9 asterisk -vvvvcg 9>valgrind.txt
|
|
|
|
Where /usr/src/asterisk/ is location of asterisk source code.
|
|
|
|
4. Reproduce the issue. Following the manifestation of the issue (or when
|
|
the process crashes), upload the valgrind.txt to the issue tracker.
|
|
|
|
Please note that even if valgrind prevents Asterisk from crashing, the
|
|
information logged may STILL be of use to developers, so please upload the
|
|
resulting log file whether Asterisk crashes or not.
|
|
|