| Summary: | ASTERISK-26852: res_sorcery_config: Crash when allocating | ||
| Reporter: | Ross Beer (rossbeer) | Labels: | |
| Date Opened: | 2017-03-10 03:19:11.000-0600 | Date Closed: | 2020-01-14 11:13:42.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/Sorcery |
| Versions: | 13.14.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Fedora 23 | Attachments: | ( 0) backtrace_2017-03-10_clean.txt |
| Description: | A segfault occurs when calling _ast_calloc | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-03-10 03:19:13.309-0600 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-03-12 18:26:03.642-0500 Your backtrace appears to contain a memory corruption. We need one or both of the following items to continue investigation of the issue: 1. Valgrind output. See https://wiki.asterisk.org/wiki/display/AST/Valgrind for instructions on how to use Valgrind with Asterisk. 2. MALLOC_DEBUG output. See https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag for instructions on how to use the MALLOC_DEBUG option. Note that MALLOC_DEBUG and Valgrind are mutually exclusive options. Valgrind output is preferable, but will be more system resource intensive and may be difficult to get on a production system. In such a case, you may have better luck getting the necessary output from MALLOC_DEBUG. By: Asterisk Team (asteriskteam) 2017-03-27 12:00:02.263-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 | ||