[asterisk-bugs] [Asterisk 0015316]: [patch] Segfault after Manager Bridge

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15316 
====================================================================== 
Reported By:                vmarrone
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15316
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.1.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-06-11 11:51 CDT
Last Modified:              2009-09-17 10:46 CDT
====================================================================== 
Summary:                    [patch] Segfault after Manager Bridge
Description: 
I have configured the dialplan like this:

exten => _X.,1,Ringing()
exten => _X.,2,Wait(1000)
exten => _X.,3,Goto(2)
exten => _X.,4,Answer()
exten => _X.,5,Goto(2)

When a call comes in the context, by AMI, I can redirect the created
channel to 4th priority for answer the call. 
When I receive a Channel State UP for this channel, always by AMI, I can
Originate an Async new Call and put it on the same context.
When I receive the Success Originate Response Event, finally make the
Bridge for the two channels obtained.

This goes very well almost every time, and the two channels are connected
between them.


If one of the channels, DURING THE EXECUTION OF THE BRIDGE, hangups,
asterisk crashes.




====================================================================== 

---------------------------------------------------------------------- 
 (0110873) svnbot (reporter) - 2009-09-17 10:46
 https://issues.asterisk.org/view.php?id=15316#c110873 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 219199

_U  branches/1.6.1/
U   branches/1.6.1/include/asterisk/cdr.h
U   branches/1.6.1/include/asterisk/channel.h
U   branches/1.6.1/main/channel.c

------------------------------------------------------------------------
r219199 | mnicholson | 2009-09-17 10:46:05 -0500 (Thu, 17 Sep 2009) | 24
lines

Merged revisions 219139 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r219139 | mnicholson | 2009-09-17 10:18:01 -0500 (Thu, 17 Sep 2009) | 17
lines
  
  Merged revisions 219136 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r219136 | mnicholson | 2009-09-17 09:58:39 -0500 (Thu, 17 Sep 2009) |
10 lines
    
    Prevent a potential race condition and crash when hanging up a channel
by removing the channel from the channel list before begining channel tear
down.
    
    This fix may potentially cause problems with CDR backends that access
the channel a CDR is associated with via the channel list.  This fix makes
the channel unavabile at the time when the CDR backend is invoked.  This
has been documented in include/asterisk/cdr.h.
    
    (closes issue https://issues.asterisk.org/view.php?id=15316)
    Reported by: vmarrone
    Tested by: mnicholson
    
    Review: https://reviewboard.asterisk.org/r/362/
  ........
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=219199 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-17 10:46 svnbot         Checkin                                      
2009-09-17 10:46 svnbot         Note Added: 0110873                          
======================================================================