[asterisk-bugs] [Asterisk 0013459]: Crash - call to agent channel when agent is logging in.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13459 
====================================================================== 
Reported By:                zerohalo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13459
Category:                   Channels/chan_agent
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.20 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-10 14:22 CDT
Last Modified:              2008-09-11 13:36 CDT
====================================================================== 
Summary:                    Crash - call to agent channel when agent is logging
in.
Description: 
When logging as an Agent via manager call and a call was being delivered to
the queue asterisk locked up and the CLI became unresponsive. BT attached.
====================================================================== 

---------------------------------------------------------------------- 
 (0092355) putnopvut (administrator) - 2008-09-11 13:36
 http://bugs.digium.com/view.php?id=13459#c92355 
---------------------------------------------------------------------- 
I wasn't able to get any useful information off the core file due to ??
stack frames in the threads which were waiting for locks. I already
indicated this in an e-mail to you, but I just want to repeat this here in
case this same problem occurs to anyone else.

What's needed here is the output of the command "core show locks" when
this deadlock occurs. If I can get output of that, then it will help me in
debugging the issue. If the CLI is unresponsive as zerohalo indicated, I
usually find that starting a new remote console with asterisk -r allows me
to start entering commands properly again. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-11 13:36 putnopvut      Note Added: 0092355                          
======================================================================