[asterisk-bugs] [Asterisk 0010571]: SIP hairpin invokes Local within app_dial to produce a crash.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10571 
====================================================================== 
Reported By:                dtyoo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10571
Category:                   Applications/app_dial
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:            1.4.9  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-27-2007 08:43 CDT
Last Modified:              10-10-2007 02:06 CDT
====================================================================== 
Summary:                    SIP hairpin invokes Local within app_dial to produce
a crash.
Description: 
We are getting crashes in app_voicemail on a fairly regular basis.  I'm
still working on steps to re-produce, but I thought I would post the
backtraces here in case someone could glean anything from them.  I will
update if I can figure out the steps to re-produce.
====================================================================== 

---------------------------------------------------------------------- 
 Ivan - 10-10-07 02:06  
---------------------------------------------------------------------- 
Corydon76 - I comment not only debug code. There is a WATCHDOG to look at
correct owning for free mutex in three cases:
1. unlock mutex
2. wait condition in mutex
3. wait timed condition in mutex
Is it realy need?
Except for that, "reentrancy" counter is using in <chan_h323.c> and
<channels.c> with debug perposes (in DEBUG_THREADS mode).
To fill "reentrancy" correct there are two ways:
1. Use atomic function to increment or decrement counter (it more quickly
than way 2 but demands more experience in implementation)
2. Use global (or local - will be more quickly but more prodigally)
critical section (specific mutex in Linux) in that debug mode for perfom
"read\write" operation under "reentrancy" counter (slower than way 1 but 
more suitable for the debugging purposes)
I think what to do it the one who wrote this debugging should.
At the personal request (ICQ:138890162) I can render consultation or make. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-10-07 02:06  Ivan           Note Added: 0071745                          
======================================================================