| Summary: | ASTERISK-26152: Crash issue in ast_format_get_type of format.c | ||||
| Reporter: | Denis S.Davydov (denis.davydov) | Labels: | |||
| Date Opened: | 2016-06-26 14:15:39 | Date Closed: | 2016-06-26 14:22:08 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | |||
| Versions: | 13.9.1 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Virtual Machine on ESXi6 (VM Version 11, 4vCPU, 16Gb RAM), OS: CentOS release 6.8 (Final) x86_84 | Attachments: | ( 0) backtrace5.txt ( 1) full5.txt | ||
| Description: | Program terminated with signal 11, Segmentation fault.
#0 0x0000000000521d21 in ast_format_get_type (format=0xdeaddeaddeaddead) at format.c:385 385 return format->codec->type; backtrace.txt and full.txt are in attachment. I can give you configuration snippet by your request. Compiled flags on my Asterisk-PBX is DONT_OPTIMIZE, COMPILE_DOUBLE, LOADABLE_MODULES, BETTER_BACKTRACES, MALLOC_DEBUG, BULD_NATIVE. Mmlog useless, there's nothing. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-06-26 14:15:40.197-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2016-06-26 14:22:08.486-0500 Closing as this is the same underlying problem as ASTERISK-26149 | ||||