[asterisk-bugs] [JIRA] (ASTERISK-28008) Asterisk crash signal 11, Segmentation fault

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-28008:
--------------------------------------------

Backtraces just indicate that memory corruption happened.  Memory corruption rarely gives evidence of what causes it in a backtrace because crashes happen well after the cause.  You have only provided a backtrace, indicated that it only happened once, and you are reporting against an old version of Asterisk.  This is not enough information to narrow down what happened.  There is no secret formula to finding and fixing memory corruption bugs.

There are 1971 commits between 13.13.0 and the current 13.22.0 release.  There are 119 more commits accumulated for a future 13.23.0 release.  I know that some of those commits fixed memory corruption issues.

> Asterisk crash signal 11, Segmentation fault
> --------------------------------------------
>
>                 Key: ASTERISK-28008
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28008
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.13.0
>         Environment: Centos 6 
>            Reporter: mohit dhiman
>            Assignee: Unassigned
>         Attachments: gdb.txt
>
>
> asterisk got crashed with signal 11, segmentation fault. i tried to debug the core dump using gdb but didn't find anything significant.
> i am attaching the output file of `thread apply all bt`.



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