[asterisk-bugs] [Asterisk 0018307]: Random Crash

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18307 
====================================================================== 
Reported By:                kvveltho
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18307
Category:                   Core/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.14 
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-11-15 05:10 CST
Last Modified:              2010-12-03 11:58 CST
====================================================================== 
Summary:                    Random Crash
Description: 
There are about 100 cc calls + 10 chanspy channels on server + 1 queue
About 80 regsitered accounts.
====================================================================== 

---------------------------------------------------------------------- 
 (0129301) aragon (reporter) - 2010-12-03 11:58
 https://issues.asterisk.org/view.php?id=18307#c129301 
---------------------------------------------------------------------- 
I am not a developer so I will not be of any help with debugging this
problem but your gdb trace is not going to be of any help since the values
in the trace are optmized out.

Please see the doc/backtrace.txt file in your Asterisk source directory.

Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the
Compiler Flags section, then:

make install

after enabling, reproduce the crash, and then execute the instructions in
doc/backtrace.txt.

When complete, attach that file to this issue report. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-03 11:58 aragon         Note Added: 0129301                          
======================================================================