[asterisk-bugs] [Asterisk 0017114]: Segfault error

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17114 
====================================================================== 
Reported By:                mpiazzatnetbug
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17114
Category:                   General
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           Older 1.4 - please test a newer version 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-03-30 04:24 CDT
Last Modified:              2010-03-30 05:56 CDT
====================================================================== 
Summary:                    Segfault error
Description: 
I get a segfault error, i don't have any message in the syslog but I foud
the core file into the tmp directory. The server has 1100 peers registered
on it.
The version of asterisk is 1.4.26.3

backtrace dump included
====================================================================== 

---------------------------------------------------------------------- 
 (0119998) davidw (reporter) - 2010-03-30 05:56
 https://issues.asterisk.org/view.php?id=17114#c119998 
---------------------------------------------------------------------- 
This isn't a segfault, it is an abort.  Specifically it is an abort by the
memory allocator.  You should at least turn on malloc debugging and see if
you can get it to reproduce.  Strictly speaking, you should follow the
instructions in doc/valgrind.txt, although you may find that the
performance hit is unacceptable, if you can't quickly reproduce the
problem.

You've either had a double close on your music on hold stream, or you have
general memory corruption. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-30 05:56 davidw         Note Added: 0119998                          
======================================================================