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

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-26017:
-----------------------------------------

Thank you for the crash report. However, we need more information to investigate the crash. Your backtrace has many values optimized out. Please follow the linked instructions to get an appropriate backtrace. While doing this, if possible test in the latest version of 13 (13.9.0 at this moment).


 Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace



> 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
>              Labels: crash
>         Attachments: 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)