[asterisk-bugs] [JIRA] (ASTERISK-23339) Segfault in __ao2_find ()

[David Brillert (JIRA)]

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

David Brillert edited comment on ASTERISK-23339 at 2/21/14 8:57 AM:
--------------------------------------------------------------------

I have reported this before but I couldn't get Asterisk rpms to compile properly with some build options we used to use for 1.4 and 1.8.
Removing those build options allows me to get a nice backtrace :D Attached
Had a production server dump on me 3 times yesterday in same place.
                
      was (Author: aragon):
    I have reported this before but I couldn't get Asterisk rpms to compile properly with some build options we sued to use for 1.4 and 1.8
Removing those build options allows me to get a nice backtrace :D Attached
Had a production server dump on me 3 times yesterday in same place.
                  
> Segfault in __ao2_find ()
> -------------------------
>
>                 Key: ASTERISK-23339
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23339
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 11.6.0, 11.7.0
>         Environment: centos 5.9 64bit
>            Reporter: David Brillert
>            Assignee: Matt Jordan
>            Severity: Critical
>         Attachments: backtrace unoptimized feb 20 2014.txt
>
>
> Segfault.  Backtrace attached.
> Asterisk was compiled with DONT_OPTIMIZE and BETTER_BACKTRACES

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