|Summary:||ASTERISK-13690: asterisk crashes when voicemail app finish to write a message|
|Reporter:||Daniel Tryba (kwark)||Labels:|
|Date Opened:||2009-03-03 15:37:03.000-0600||Date Closed:||2011-06-07 14:00:33|
|Environment:||Attachments:||( 0) bt.txt|
( 1) thread.txt
|Description:||This is the same bug as reported in http://bugs.digium.com/view.php?id=14115|
Asterisk crashed after receiving the voicemail and saying goodbye.
An up to date Debian Lenny machine
Linux rdg-gw 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 GNU/Linux
100% crashes reproducable on this machine (a HP DL3x0). I tried to reproduce this on an other such box but have no problems there. I'm not 100% sure it is the same type though.
I hope this backtrace is better than the traces in 14115 (I installed the asterisk-dbg package)
|Comments:||By: Mark Michelson (mmichelson) 2009-03-03 16:06:44.000-0600|
Unfortunately, the backtrace has optimized values in it. I'm not familiar with the asterisk-dbg package. Would it be possible for you to reproduce the crash running Asterisk under valgrind? Instructions for how to do so are located in doc/valgrind.txt of the Asterisk source. If you don't have Asterisk source because of the package you are using, you can find the instructions here as well: http://svn.digium.com/view/asterisk/branches/1.4/doc/valgrind.txt?revision=155803&view=markup
By: Daniel Tryba (kwark) 2009-03-03 16:52:25.000-0600
I'll try to get a non optimized asterisk on that machine. Might take a couple of days. Will also look into the valgrind method.
By: Daniel Tryba (kwark) 2009-03-09 13:08:00
Very strange stuff happening:
-debian package Asterisk 18.104.22.168~dfsg-3:
reproducable crashes 100% of the time after hangup
-installed the debian package compiled for debugging:
no crashes, everything works like it should
-reinstalled 22.214.171.124~dfsg-3 (package was still in archives):
no more crashes
Could this be a hardware problem? I guess I'll have to replace that machine to figure out if there is some hw problem (like bad mem).
By: Mark Michelson (mmichelson) 2009-03-09 15:04:29
I don't know if it's bad memory or some other weird state that the machine was in, but if you're not experiencing the crashes now but were previously experiencing them 100% of the time, it seems like the problem is not necessarily attributable to Asterisk.
I'm going to be bold and suspend this issue since I really think that you're not going to be able to start reproducing the crashes again. Please don't hesitate to re-open this issue if you should start having the crashes again. Thank you!