[asterisk-bugs] [JIRA] (ASTERISK-28021) backtrace.c: New crash due to double-free.

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244583#comment-244583 ] 

Asterisk Team commented on ASTERISK-28021:
------------------------------------------

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].

> backtrace.c: New crash due to double-free.
> ------------------------------------------
>
>                 Key: ASTERISK-28021
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28021
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: 13.22.0
>         Environment: Linux version 3.10.0-693.2.2.el7.x86_64 (builder at kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Tue Sep 12 22:26:13 UTC 2017
>            Reporter: Cirillo
>         Attachments: core.ANTIBES-2018-08-22T12-45-00-0300-brief.txt, core.ANTIBES-2018-08-22T12-45-00-0300-full.txt, core.ANTIBES-2018-08-22T12-45-00-0300-locks.txt, core.ANTIBES-2018-08-22T12-45-00-0300-thread1.txt
>
>
> Apparently the crash reported in https://issues.asterisk.org/jira/browse/ASTERISK-27340 doesn't went fixed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)