[asterisk-bugs] [Asterisk 0017297]: 1.6.2.7 hangs during initial module load on Darwin

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17297 
====================================================================== 
Reported By:                jcovert
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17297
Category:                   Core/Portability
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.7 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-05-06 11:48 CDT
Last Modified:              2010-05-06 12:43 CDT
====================================================================== 
Summary:                    1.6.2.7 hangs during initial module load on Darwin
Description: 
1.6.2.7 hangs in the loader when loading the first module.  It doesn't
matter whether a module is specified as pre-load or not; whatever module is
loaded first deadlocks.

I have isolated this to the call to AST_LIST_LOCK(&module_list) which
occurs in routine ast_module_register, called back from the module itself
during the call to dlopen in routine load_dynamic_module.

1.6.2.6 does not exhibit this problem.
====================================================================== 

---------------------------------------------------------------------- 
 (0121486) pabelanger (manager) - 2010-05-06 12:43
 https://issues.asterisk.org/view.php?id=17297#c121486 
---------------------------------------------------------------------- 
Are you able to provide a backtrace?
---
Debugging deadlocks:

Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags
section of menuselect. Recompile and install Asterisk (i.e. make install)

This will then give you the console command:

core show locks 

When the symptoms of the deadlock present themselves again, please provide
output of the deadlock via:

# asterisk -rx \"core show locks\" | tee /tmp/core-show-locks.txt

# gdb -se \"asterisk\" <pid of asterisk> | tee /tmp/backtrace.txt

gdb> bt
gdb> bt full
gdb> thread apply all bt

Then attach the core-show-locks.txt and backtrace.txt files to this issue.
Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-06 12:43 pabelanger     Note Added: 0121486                          
======================================================================