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

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-22875:
-------------------------------------------

Jeremy:
Your backtrace is optimized out too.  Which means Digium can't help us with a patch.
I'm having serious issues getting Asterisk to spit out an unoptimized backtrace but maybe you'll have better luck.
Try to follow the instructions at https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace and compile Asterisk with menuselect options for DONT_OPTIMIZE and BETTER_BACKTRACES

Then wait for another crash and see if your gdb output does not show <optimized out>.
That should mean you can provide a usable backtrace and help move this issue forward.
                
> CLONE - Segfault in __ao2_find ()
> ---------------------------------
>
>                 Key: ASTERISK-22875
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22875
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 11.6.0
>         Environment: centos 5.9 64bit
>            Reporter: David Brillert
>            Assignee: David Brillert
>            Severity: Critical
>         Attachments: backtrace2.txt, backtrace.txt, gdb thread apply all.txt, gdb trace.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