[asterisk-bugs] [JIRA] (ASTERISK-28587) Asterisk crash when answering a call

[Dan Cropp (JIRA)]

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

Dan Cropp commented on ASTERISK-28587:
--------------------------------------

We installed a brand new Ubuntu 16 VM installed on the VMWare ESXi having problems.
Then we installed my compiled 16.4.1 asterisk and it encountered the same problems.

My thought is to start with asterisk 16.3.0 (which we have compiled and installed on this VM server without issue).
Then, step through the list of changes from 16.3.0 to 16.4.1 patching the code with each change one at a time until I run into the change where things stop working.

> Asterisk crash when answering a call
> ------------------------------------
>
>                 Key: ASTERISK-28587
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28587
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 16.4.1
>         Environment: Ubuntu 16.04 running in a VMWare ESXi environment
>            Reporter: Dan Cropp
>            Assignee: Dan Cropp
>              Labels: fax, pjsip
>         Attachments: core.tar.gz
>
>
> Everything is fine with asterisk 16.3.0 (been running it for some time).
> We went to upgrade to 16.6.0 and encountered a crash.  I went back to 16.4.1 and replicated the crash.
> I start up Asterisk.
> Connect up to AMI socket using telnet session.
> Place a call into asterisk and see everything in telnet, and receive control of the call through AsyncAGI.
> Using telnet, I send a command to answer the call and it crashes.
> Following the getting a backtrace steps, I discovered that if I enable DONT_OPTIMIZE the crash does not happen.  I repeated the steps and recompiled verifying I don't see this if DONT_OPTIMIZE is enabled.
> I will submit the coredump once I know the issue number



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