[asterisk-bugs] [JIRA] (ASTERISK-22757) segfault in res_clialiases.so on reload

[Gareth Blades (JIRA)]

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

Gareth Blades commented on ASTERISK-22757:
------------------------------------------

Unfortunately I don't think we are going to be able to reproduce it. The server concerned had an older snapshot of a new dialplan for a customer to test and then was updated with the latest development copy. We only have live releases in version control so without having the same starting point before the reload I doubt it will crash again.
If you could let me know what changes I can make to the build options (untick all optimisation settings) that would help in the future then I can do that on our staging server so any backtraces would be more useful if it happens again in the future.
                
> segfault in res_clialiases.so on reload
> ---------------------------------------
>
>                 Key: ASTERISK-22757
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22757
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_clialiases
>    Affects Versions: 11.2.0
>         Environment: Centos 6.4 64bit
> Asterisk 11.2-cert2
> glibc-2.12-1.107.el6_4.2.x86_64
>            Reporter: Gareth Blades
>            Assignee: Gareth Blades
>         Attachments: backtrace.txt
>
>
> I performed a reload and asterisk crashed. There were a couple of new dynamic features changed and quite a lot of dialplan changes.
> kernel: asterisk[17869]: segfault at 0 ip 00007f57848b1eec sp 00007f577a558cc8 error 4 in res_clialiases.so[7f57848b1000+2000]
> backtrace attached

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira