[asterisk-bugs] [Asterisk 0014296]: chan_dahdi segfaulting (may be related to Bridge() application).

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14296 
====================================================================== 
Reported By:                kebl0155
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14296
Category:                   Channels/chan_dahdi
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-21 08:26 CST
Last Modified:              2009-01-26 16:42 CST
====================================================================== 
Summary:                    chan_dahdi segfaulting (may be related to Bridge()
application).
Description: 
Hi,

We changed one of our apps to use the new Bridge() command today.  Since
then we've had two segfault/core dumps in chan_dahdi.

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

---------------------------------------------------------------------- 
 (0098801) kebl0155 (reporter) - 2009-01-26 16:42
 http://bugs.digium.com/view.php?id=14296#c98801 
---------------------------------------------------------------------- 
Hello,

Since posting the bug I've been able to produce a work-around by adding a
one second delay between the Bridge() command, and the ensuing Hangup()
command that is run when one or other of the callers hangs up the phone,
like this:

exten => _9XXX,n,Bridge(${CALLERCHANNEL})
exten => _9XXX,n,Wait(1)
exten => _9XXX,n,Hangup

This has solved the problem in that we're no longer getting the core dumps
or Fixup Failed messages. 

I think the problem was happening because Hangup() was being executed
before the Bridge mechanism had completely finished unlinking the
channels.

Unfortunately I can't compromise the customer's call centre by removing
the work-around as this is a production system (i.e. they'll shout at
me...), so I am unable to produce the further core dumps requested, as I'm
sure you can appreciate!

None the less I have uploaded a full gdb output from the last core dump -
I hope it is of some use. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-26 16:42 kebl0155       Note Added: 0098801                          
======================================================================