[asterisk-bugs] [Asterisk 0014043]: Crash (included coredump)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14043 
====================================================================== 
Reported By:                ibc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14043
Category:                   General
Reproducibility:            unable to reproduce
Severity:                   block
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-09 12:04 CST
Last Modified:              2008-12-10 12:26 CST
====================================================================== 
Summary:                    Crash (included coredump)
Description: 
Asterisk 1.4.22 has crashed when handling around 60 SIP channels. This
server supports usually much more traffic (~ 500 SIP channels).

Before 1.4.22 version, this error (crash) occurred very often during the
max calls period (once each 2 days). That error seemed to be fixed in
1.4.22, until now. Of course, it could be a very different issue.

There are not Zap devices, just SIP users and SIP trunks.
We do CDR against an external MySQL server via ODBC and use dynamic
realtime dialplan.

GDB output is attached.
====================================================================== 

---------------------------------------------------------------------- 
 (0096119) Corydon76 (administrator) - 2008-12-10 12:26
 http://bugs.digium.com/view.php?id=14043#c96119 
---------------------------------------------------------------------- 
Crud, you have corrupted memory.  We're going to need to do this under
valgrind.  See doc/valgrind.txt. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-10 12:26 Corydon76      Note Added: 0096119                          
======================================================================