Merged revisions 88116 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r88116 | tilghman | 2007-11-01 12:17:56 -0500 (Thu, 01 Nov 2007) | 2 lines Add some notes on using valgrind ........ git-svn-id: http://svn.digium.com/svn/asterisk/trunk@88117 f38db490-d61c-443f-a65b-d21fe96a405b
This commit is contained in:
parent
29e524f0b8
commit
23373716db
|
@ -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.
|
||||||
|
|
Reference in New Issue