[asterisk-bugs] [Asterisk 0011838]: SIGSEGV ast_read from ast_channel_bridge/..generic_bridge, chan->tech==0x2

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11838 
====================================================================== 
Reported By:                stuarth
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   11838
Category:                   Core/PBX
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 duplicate
Duplicate:                  11811
Fixed in Version:           
====================================================================== 
Date Submitted:             01-24-2008 12:20 CST
Last Modified:              01-28-2008 06:41 CST
====================================================================== 
Summary:                    SIGSEGV ast_read from
ast_channel_bridge/..generic_bridge, chan->tech==0x2
Description: 
Random segfaults on 1.4.17 every couple of days or so - nothing abnormal
logged (debug 10/verbose 10). This is a moderately busy SIP-only PBX, with
realtime (ODBC) queues and AMI in use. I'll attach a full backtrace
(DONT_OPTIMIZE), slightly sanitized.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0011811 Crash. bridged->chan is null
====================================================================== 

---------------------------------------------------------------------- 
 file - 01-28-08 06:41  
---------------------------------------------------------------------- 
The current underlying issue here (since the original has been solved) is
actually 11811. Check there for progress. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-28-08 06:41  file           Relationship added       duplicate of 0011811
01-28-08 06:41  file           Duplicate ID             0 => 11811          
01-28-08 06:41  file           Status                   feedback => resolved
01-28-08 06:41  file           Resolution               open => duplicate   
01-28-08 06:41  file           Assigned To               => file            
01-28-08 06:41  file           Note Added: 0081264                          
======================================================================