| Summary: | ASTERISK-28008: Asterisk crash signal 11, Segmentation fault | ||
| Reporter: | Mohit Dhiman (mohitdhiman) | Labels: | |
| Date Opened: | 2018-08-09 05:18:42 | Date Closed: | 2020-01-14 11:14:05.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 13.13.0 | Frequency of Occurrence | One Time |
| Related Issues: | |||
| Environment: | Centos 6 | Attachments: | ( 0) gdb.txt |
| Description: | asterisk got crashed with signal 11, segmentation fault. i tried to debug the core dump using gdb but didn't find anything significant.
i am attaching the output file of `thread apply all bt`. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-08-09 05:18:44.162-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: Richard Mudgett (rmudgett) 2018-08-09 07:39:23.203-0500 It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists. Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions Based on the backtrace I suspect you had memory corruption. Asterisk 13.13.0 is over a year and a half old and there have been memory corruption issues fixed since then. By: Mohit Dhiman (mohitdhiman) 2018-08-09 08:48:58.529-0500 can you please at least tell me what kind of memory corruption are we talking here or where exactly i can look for it into the asterisk code or possibly the reason for memory corruption. By: Richard Mudgett (rmudgett) 2018-08-09 10:56:45.490-0500 Backtraces just indicate that memory corruption happened. Memory corruption rarely gives evidence of what causes it in a backtrace because crashes happen well after the cause. You have only provided a backtrace, indicated that it only happened once, and you are reporting against an old version of Asterisk. This is not enough information to narrow down what happened. There is no secret formula to finding and fixing memory corruption bugs. There are 1971 commits between 13.13.0 and the current 13.22.0 release. There are 119 more commits accumulated for a future 13.23.0 release. I know that some of those commits fixed memory corruption issues. By: Mohit Dhiman (mohitdhiman) 2018-08-09 11:10:26.617-0500 ok thanks, i'll upgrade the asterisk version. By: Richard Mudgett (rmudgett) 2018-08-09 11:21:48.182-0500 Waiting for verification on newer version. By: Asterisk Team (asteriskteam) 2018-08-23 12:00:02.257-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||