[asterisk-bugs] [JIRA] (ASTERISK-26877) app_queue: Crash when seeing if a member can be rung

[Kevin Farrell (JIRA)]

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

Kevin Farrell edited comment on ASTERISK-26877 at 3/20/17 8:41 AM:
-------------------------------------------------------------------

Hi,

I did not alter the source code in any way; I compiled Asterisk from source a bunch of times on the server, so maybe this had an impact on the code?  Also, I run a FreePBX GUI over Asterisk, so maybe therein lies the issue?


was (Author: kfpelletier):
Hi,

I did not alter the source code in any way; I compiled Asterisk from source a bunch of times on the server, so maybe this had an impact on the code?  Also, I run a FreePBX GUI over Asterisk, so many therein lies the issue?

> app_queue: Crash when seeing if a member can be rung
> ----------------------------------------------------
>
>                 Key: ASTERISK-26877
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26877
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.13.1
>         Environment: Centos 6.7 64bit
>            Reporter: Kevin Farrell
>            Assignee: Unassigned
>         Attachments: backtrace.txt, core.zip
>
>
> Hi,
> I am getting Core Dumps which, when generated, drop all concurrent calls.  I have tried recompiling Asterisk to three different version; 13.0.0, 13.13.1 and am now on 13-cert.  In all cases, the same kind of message is generated by the core dump.  Here is a copy of the message:
> Program terminated with signal 11, Segmentation fault.
> #0  0x00007fe9fc4a44d7 in can_ring_entry (qe=0x7fe9f471e2e0, tmp=0x7fea3c25ba10, busies=0x7fe9f471e1d4) at app_queue.c:4167
> 4167            if (call->member->in_call && call->lastqueue->wrapuptime) {
> I hope you can recommend a resolution to this problem; any help would be greatly appreciated.  Please do not hesitate to ask me for some more information as I would gladly provide it.



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