[asterisk-dev] How to catch the source of a deadlock?

[Russell Bryant]

On Tue, Jan 27, 2015 at 7:01 AM, Yousf Ateya <y.ateya at starkbits.com> wrote:

> Dear,
>
> While investigating iax2 bug ASTERISK-24478
> <https://issues.asterisk.org/jira/browse/ASTERISK-24478?focusedCommentId=224584&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-224584>;
> I found some dead locks. Which happens very often in my setup.
>
> I tried to debug the problem to know why this deadlock happens; but each
> time I got lost in huge logs and many scheduler/astobj2 details.
>
> Is there any efficient way to debug deadlocks in asterisk?
>

Have you seen the DEBUG_THREADS compile time option and the "core show
locks" CLI command?

https://wiki.asterisk.org/wiki/display/AST/CLI+commands+useful+for+debugging

-- 
Russell Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20150127/1e3e6e50/attachment-0001.html>