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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26017:
------------------------------------------

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

> 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
>
> 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)