[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=212300#comment-212300 ] 

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

That is a tough decision.
We also manage our own rpms through a build system.  And back in the 1.4 days it was an easy decision to make.  We built our rpms with all debug options on and the performance hit did not outweigh the need to get access to sufficient backtraces for problem resolution.  Since then the performance hit in 1.8 and 11 is more remarkable.  I definitely wouldn't compile with DEBUG_THREADS since that really affects performance.
I would do some benchmarking:
1. Compare CPU load and voice quality with and without the standard backtrace requirements.
2. Test the gdb output on multiple servers and OS versions to see if your .deb versions provide the necessary unoptimized output.

Perhaps you should build two .deb versions; Production Vs. Debug and put them in your repos and only allow one or the other to be installed by the package manager.
                
> 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