[Home]

Summary:ASTERISK-20594: Asterisk crash
Reporter:Osvaldo Tuphiq Smera Neto (osvaldo)Labels:
Date Opened:2012-10-22 14:42:38Date Closed:2012-11-27 17:50:34.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Addons/cdr_mysql Applications/app_mixmonitor Applications/app_originate Applications/app_queue Resources/res_musiconhold
Versions:1.8.14.0 Frequency of
Occurrence
Frequent
Related
Issues:
Environment:SO Debian 6, 3 gateways GSM, voip.Attachments:( 0) backtrace.txt
( 1) backtrace2310.txt
( 2) backtrace2410.txt
Description:The asterisk on a frequency not to logic. The asterisk was compiled with each crahs DONT_OPTIMIZE and a core file is generated. The end of each file is:

I have attached files backstrace.



What to do to solve this problem?
Comments:By: Matt Jordan (mjordan) 2012-10-23 23:59:34.125-0500

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!



By: Osvaldo Tuphiq Smera Neto (osvaldo) 2012-10-24 14:57:33.631-0500

Ok. I will follow your suggestions and guidance on Valgrind. I have attached two files backstace.


Thank you!
Osvaldo Neto Smera

By: Rusty Newton (rnewton) 2012-11-08 15:51:22.142-0600

Putting this back in Feedback since we are still waiting on Valgrind output from reporter.

By: Rusty Newton (rnewton) 2012-11-27 17:50:27.667-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