mirror of
https://github.com/asterisk/asterisk.git
synced 2025-10-31 02:37:10 +00:00
950528b638
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r89103 | tilghman | 2007-11-07 22:55:19 -0600 (Wed, 07 Nov 2007) | 2 lines Typo ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@89104 65c4cc65-6c06-0410-ace0-fbb531ad65f3
20 lines
809 B
Plaintext
20 lines
809 B
Plaintext
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.
|
|
|