[asterisk-bugs] [JIRA] (ASTERISK-22093) Deadlock in chan_local

David Brillert (JIRA) noreply at issues.asterisk.org
Thu Jul 18 08:28:03 CDT 2013


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

David Brillert commented on ASTERISK-22093:
-------------------------------------------

DEBUG_THREADS is not enabled in the build and the gdb shows a lot of <value optimized out>.
The system is a very busy production system and would not survive DEBUG_THREADS.
Is there another build option I could use to get the required locking data?
Or is there enough info in the GDB trace to help with a patch?
This is a subversion build of Asterisk 11 r391794
                
> Deadlock in chan_local
> ----------------------
>
>                 Key: ASTERISK-22093
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22093
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local
>    Affects Versions: 11.5.0
>            Reporter: David Brillert
>            Severity: Critical
>         Attachments: gdb thread apply all bt.txt
>
>
> Third deadlock in two weeks.
> Asterisk not built with NOT_OPTIMIZED or thread debug options.
> The best I could do was attach GDB to Asterisk PID and get a thread apply all BT (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



More information about the asterisk-bugs mailing list