[asterisk-bugs] [JIRA] (ASTERISK-26017) Segmentation Fault in Pre-Dial Handlers

[Mateusz (JIRA)]

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

Mateusz commented on ASTERISK-26017:
------------------------------------

Hi,
we have compiled 13.1 cert version with DONT_OPTIMIZE. I have attached backtrace.

We have CentOS 6.5.

Average load is 11000 calls per day. Something about half part of this statistic is outbound calls where we using this macro.
This outbound calls are initialized by callfiles.  

We have idea that our problem could be connected or similar to https://issues.asterisk.org/jira/browse/ASTERISK-25603, but we are not sure about it. 

I have attached new backtrace.

Please, let me know if you want some more informations. 

Best regards, 
Mateusz.


> Segmentation Fault in Pre-Dial Handlers
> ---------------------------------------
>
>                 Key: ASTERISK-26017
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26017
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.1.0, 13.2.0, 13.6.0
>            Reporter: Mateusz
>            Assignee: Rusty Newton
>              Labels: crash
>         Attachments: backtrace.txt, newest_backtrace.txt
>
>
> Hi, 
> in our company we are using an pre-dial macro and in the very last step in this macro ( Return() ) we occasionally get an segmentation fault. 
> We have checked three version of Asterisk. 
> Out handler:
> {code}
>  exten => outbound,1,NoOp()
> same => n,Set(CHANNEL(userfield)=${CHANNEL(userfield)}|calls_id:${ARG1})
> same => n,CELGenUserEvent(DIALED_AT)
> same => n,Return()
> {code}
> I have attached an backtrace. 



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