[Home]

Summary:ASTERISK-25073: Asterisk crash by ast_format_cap_append
Reporter:Roberto (tel.medola)Labels:
Date Opened:2015-05-09 10:46:44Date Closed:2015-06-09 08:00:49
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:11.15.0 Frequency of
Occurrence		Frequent
Related
Issues:
is related toASTERISK-21737 [patch] - Crash during transfer from DAHDI/SIP to SIP/SIP in ast_format_cap_append called from remote bridge loop
Environment:Asterisk 11.15.0 Centos 6.5 - Linux 2.6.32-431.29.2.el6.x86_64 x86_64 Hardware 192GB Ram - 32 cores xeonAttachments:( 0) backtrace.txt
Description:During normal use of the day, the asterisk simply falls. Several times during the day.
I took the core file and extracts the backtrace that is attached to the call.

Analyzing the backtrace even thread "Thread 1 (Thread 0x7f13004e7700 (LWP 17043))" using the tool "ast_format_cap_append".
I found an error similar to this in (ASTERISK-21737). In versions greater than my (11.17.1 for example), this bug has already been fixed?

Thanks
Comments:By: Rusty Newton (rnewton) 2015-05-15 16:29:28.832-0500

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Rusty Newton (rnewton) 2015-05-15 16:31:36.174-0500

Specifically, follow the instructions for the backtrace as we need Asterisk to be compiled with BETTER_BACKTRACES and DONT_OPTIMIZE.

Also, provide a debug log leading up to the crash: [Collecting Debug|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information]


By: Roberto (tel.medola) 2015-05-26 06:31:28.005-0500

It is very complicate to catch.

Please, close this issue.

Thanks.
By: Rusty Newton (rnewton) 2015-06-09 08:00:49.873-0500

I've spoken with a developer or two and without further information, debug and reproduction steps we can't really tell how Asterisk got into the state that it is in.

Thanks and feel free to open a new issue in the future if you are able to gather an Asterisk log with debug alongside the crash or narrow down how to reproduce.