Skip to content
Snippets Groups Projects
Commit 49631e20 authored by Tilghman Lesher's avatar Tilghman Lesher
Browse files

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: https://origsvn.digium.com/svn/asterisk/trunk@88117 65c4cc65-6c06-0410-ace0-fbb531ad65f3
parent 9a7ce542
No related branches found
No related tags found
No related merge requests found
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.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment