[asterisk-bugs] [Asterisk 0010997]: Asterisk 1.4.13 segfaults at least once daily

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10997 
====================================================================== 
Reported By:                aragon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10997
Category:                   Core-General
Reproducibility:            N/A
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-16-2007 10:52 CDT
Last Modified:              10-16-2007 12:48 CDT
====================================================================== 
Summary:                    Asterisk 1.4.13 segfaults at least once daily
Description: 
System segfaults at least once daily
Started segfaulting after upgrade from 1.2.24 to 1.4.11
Tried many upgrades in increments
1.4.11
1.4.12
1.4.12 SVN
1.4.12.1
1.4.13
Problem still exists in 1.4.13

I dont know what steps are needed to reproduce.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 10-16-07 12:48  
---------------------------------------------------------------------- 
aragon:  if the next backtrace ends in a crash inside malloc(), there's no
need to post another backtrace.  What we need, instead, is the log of
exactly what happens just before the crash.  If you could post the last 5
seconds worth of activity from the "full" log, that should help.

The problem is one of memory corruption, so we'll need to track down
exactly what is stomping on the malloc structures (which causes malloc to
abort(3)). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-16-07 12:48  Corydon76      Note Added: 0072097                          
======================================================================