[asterisk-bugs] [Asterisk 0016767]: [patch] Deadlock between handle_request_do and do_devstate_changes

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16767 
====================================================================== 
Reported By:                lmsteffan
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   16767
Category:                   Channels/chan_sip/General
Reproducibility:            unable to reproduce
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                       SWP-869 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 238602 
Request Review:              
====================================================================== 
Date Submitted:             2010-02-03 20:47 CST
Last Modified:              2010-02-25 00:37 CST
====================================================================== 
Summary:                    [patch] Deadlock between handle_request_do and
do_devstate_changes
Description: 
title says it all :-)
====================================================================== 

---------------------------------------------------------------------- 
 (0118531) lmsteffan (reporter) - 2010-02-25 00:37
 https://issues.asterisk.org/view.php?id=16767#c118531 
---------------------------------------------------------------------- 
I am afraid this will be difficult as it's our main (production) server and
it's running under fairly heavy load, so I'm not too enthusiastic about
installing gdb, setting DON'T OPTIMIZE (but I guess I will anyway), and
above all interrupting all traffic while performing the gdb commands. Is
there some set of options (under the compile flags) that I could use to
dump core and *then* perform the gdb backtrace ? I think that once I saw
options like "crash on error" or something but never ventured to try
them... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-25 00:37 lmsteffan      Note Added: 0118531                          
======================================================================