[asterisk-bugs] [Asterisk 0017438]: Asterisk cores @ 110 calls

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17438 
====================================================================== 
Reported By:                dcabot
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17438
Category:                   Core/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.7 
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-06-01 12:35 CDT
Last Modified:              2010-06-01 12:52 CDT
====================================================================== 
Summary:                    Asterisk cores @ 110 calls
Description: 
Load testing IVR using SIPP.  Asterisk cores at 110 calls.  IVR using PHP
FastAGI.
====================================================================== 

---------------------------------------------------------------------- 
 (0122714) pabelanger (manager) - 2010-06-01 12:52
 https://issues.asterisk.org/view.php?id=17438#c122714 
---------------------------------------------------------------------- 
Your backtrace is optimized out (see below), please upload a new one.
---
Thank you for your bug report. In order to move your issue forward, we
require a backtrace from the core file produced after the crash. 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. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-01 12:52 pabelanger     Note Added: 0122714                          
======================================================================