Summary: | ASTERISK-27010: Asterisk Crash with core dump | ||
Reporter: | Sebastian Gutierrez (sum) | Labels: | |
Date Opened: | 2017-05-19 14:18:39 | Date Closed: | 2020-01-14 11:13:52.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | |
Versions: | 13.15.0 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ( 0) backtrace.txt | |
Description: | I attach the full backtrace of the crash. | ||
Comments: | By: Asterisk Team (asteriskteam) 2017-05-19 14:18:40.376-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) 2017-05-22 07:03:12.640-0500 The backtrace does not provide enough information about how a bridged channel got into a state where its channel was no longer valid. We would also need to see a console log leading up to the crash to trace the path and interaction. By: Asterisk Team (asteriskteam) 2017-06-05 12:00:00.988-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 |