| Summary: | ASTERISK-26958: Segfault ast_format_cmp | ||
| Reporter: | Ross Beer (rossbeer) | Labels: | |
| Date Opened: | 2017-04-24 10:08:13 | Date Closed: | 2020-01-14 11:14:12.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_rtp_asterisk |
| Versions: | GIT | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Fedora 23 | Attachments: | ( 0) backtrace_24-04-2017_clean.txt |
| Description: | Asterisk segfaults when comparing codecs between and invite and configuration.
| ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-04-24 10:08:14.015-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: Rusty Newton (rnewton) 2017-04-26 15:09:34.215-0500 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Rusty Newton (rnewton) 2017-04-26 15:10:15.490-0500 In addition to debug if you can get a non-optimized trace that would be awesome. There is a ton of optimizations in the attached trace. By: Asterisk Team (asteriskteam) 2017-05-11 12:00:01.950-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 | ||