Summary:ASTERISK-21098: Asterisk core dumps
Reporter:Sean Coverdale (scov)Labels:
Date Opened:2013-02-14 15:24:42.000-0600Date Closed:2013-03-07 09:56:17.000-0600
Versions: Frequency of
Environment:Asterisk built by palosanto @ rpmbuild64-2.elastix.palosanto.com on a x86_64 running Linux on 2012-05-02 21:16:30 UTC Linux phone.travelgold.com 2.6.18-308.8.2.el5 #1 SMP Tue Jun 12 09:58:12 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux HP Proliant DL380G6 Server Intel Xeon E5520 (2.26GHz, 80W, DDR3-1066, 8MB L3 Cache) Attachments:( 0) backtrace.txt
( 1) core-show-locks.txt
( 2) gdb.txt
Description:We have asterisk elastix distro running in a production environment. Everything seems to be working. However, every 2-4 weeks the asterisk process core dumps.
Comments:By: Sean Coverdale (scov) 2013-02-14 15:32:45.867-0600

Backtrace information

By: Richard Mudgett (rmudgett) 2013-02-14 16:15:47.787-0600

Your backtrace appears to contain memory corruption and we require valgrind output in order to move this issue forward. Please see https://wiki.asterisk.org/wiki/display/AST/Valgrind for more information about how to produce debugging information. Thanks!

If you are using voicemail, I think there was a memory corruption fix made after v1.8.12.

Also v1.8.20 enhanced MALLOC_DEBUG to better find memory corruption problems since valgrind cannot be used in many environments for performance reasons.  MALLOC_DEBUG puts its findings in /var/log/asterisk/mmlog.

By: Matt Jordan (mjordan) 2013-03-07 09:56:11.905-0600

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines