[Home]

Summary:ASTERISK-25822: Segmentation fault in _int_malloc()
Reporter:Marius Cojocariu (marius)Labels:
Date Opened:2016-02-29 09:26:24.000-0600Date Closed:2020-01-14 11:13:51.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:13.5.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) bt.txt
( 1) bt_full.txt
( 2) thread_apply_all_bt.txt
Description:Asterisk version:

{code}
asterisk*CLI> core show version
Asterisk 13.5.0 built by asterisk @ asterisk.digitalya.ro on a x86_64 running Linux on 2016-01-05 10:30:05 UTC
{code}

Small part of stack trace:
{code}
#0  0x00007ff852524188 in _int_malloc () from /lib64/libc.so.6
#1  0x00007ff8525247ed in calloc () from /lib64/libc.so.6
#2  0x00000000005f16fb in _ast_calloc (num=1, len=2944, file=0x69fcdb "astobj2.c", lineno=545, func=0x69ff40 "internal_ao2_alloc") at /usr/local/src/asterisk/asterisk-13.5.0/include/asterisk/utils.h:573
#3  0x000000000045cf98 in internal_ao2_alloc (data_size=2856, destructor_fn=0x4b05a3 <ast_channel_destructor>, options=0, file=0x69fcdb "astobj2.c", line=630, func=0x69ff29 "__ao2_alloc") at astobj2.c:545
{code}
Comments:By: Asterisk Team (asteriskteam) 2016-02-29 09:26:25.333-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: Marius Cojocariu (marius) 2016-02-29 09:27:05.946-0600

Attached results for bt, bt full and thread apply all bt commands.
By: Rusty Newton (rnewton) 2016-02-29 13:18:20.371-0600

Marius,

Please provide the following information on the three crashes you have reported. Provide the answers or required information on each of the issues respectively:

* Can you reproduce the issue?
** If you can, please attach a guide on how to reproduce the crash including all configuration necessary.
* Do all three crashes occur on the same machine/instance of Asterisk?
* Can you test against the latest version of Asterisk 13 to see if these crashes still occur?
**  Be aware there has been security fixes since your version and you should upgrade to 13.7.2 to get the fixes.
By: Rusty Newton (rnewton) 2016-02-29 13:21:23.285-0600

In addition please provide any Asterisk log that was captured in the minutes leading up to the crash.

Preferably if you can reproduce the issue then gather a debug log as per the [instructions on the wiki|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information].
By: Asterisk Team (asteriskteam) 2016-03-15 12:00:01.419-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