[asterisk-bugs] [Asterisk 0010765]: Crash with "Segmentation fault" in zap internal timers processing

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Sep 25 08:13:57 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10765 
====================================================================== 
Reported By:                Ivan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10765
Category:                   Channels/chan_zap
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-20-2007 01:32 CDT
Last Modified:              09-25-2007 08:13 CDT
====================================================================== 
Summary:                    Crash with "Segmentation fault" in zap internal
timers processing
Description: 
Seems like "race condition" effect in channel.c (2255) - no more "chan"
object is accessible in then method generator_force at line:
1847            generate = chan->generator->generate;
====================================================================== 

---------------------------------------------------------------------- 
 Ivan - 09-25-07 08:13  
---------------------------------------------------------------------- 
I found 100% conditions for reproducibility. 
Test system: 
1. Asterisk without addons
2. Internal timers on zaptel driver
3. Attended Transfer on # symbol
4. MixMonitor on all connection
Actions:
 2 SIP Terminal connected. One of there mark # (Attended Transfer) and
dial the number of third SIP terminal that is BUSY now. After 3-10 attempts
the crash happends. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-25-07 08:13  Ivan           Note Added: 0071069                          
======================================================================




More information about the asterisk-bugs mailing list