[asterisk-bugs] [JIRA] (ASTERISK-26545) Asterisk core dump while sending MWI with chan_sip, (in sip_send_mwi_to_peer at chan_sip.c)

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-26545:
--------------------------------------------

Those FRACK messages also come with a stack probe backtrace to show where the bad ao2 object reference is being done.  Unfortunately, those backtraces aren't very useful because you don't have BETTER_BACKTRACES enabled (DONT_OPTIMIZE would also be a plus).

Asterisk has had "bad magic number" and "user_data is NULL" ERROR messages for quite awhile, but only recently were they changed to get a backtrace for where they are happening in the code.  It has always indicated a bug when you get the "bad magic number" or "user_data is NULL" messages.

The crashes may be caused by the fix for ASTERISK-25468

> Asterisk core dump while sending MWI with chan_sip, (in sip_send_mwi_to_peer at chan_sip.c)
> -------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26545
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26545
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.12.1
>         Environment: CentOS 6.8 64bit Mysql 5.1
>            Reporter: Leandro Dardini
>            Assignee: Unassigned
>            Severity: Critical
>         Attachments: backtrace-Ahmed.txt, backtrace-Robert.txt, frack2.txt, frack.txt
>
>
> I started upgrading servers from 13.2.0 to 13.12.1 and some started to crash for segmentation fault. Function involved seems always sip_send_mwi_to_peer



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