[asterisk-bugs] [Asterisk 0018421]: Segmentation Fault with flag LOW_MEMORY

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18421 
====================================================================== 
Reported By:                lgfsantos
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18421
Category:                   Core/General
Reproducibility:            always
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-12-03 11:57 CST
Last Modified:              2010-12-04 20:37 CST
====================================================================== 
Summary:                    Segmentation Fault with flag LOW_MEMORY
Description: 
Using the flag LOW_MEMORY, cross-compiling to power-pc, I have a
segmentation fault.
====================================================================== 

---------------------------------------------------------------------- 
 (0129310) pabelanger (administrator) - 2010-12-04 20:37
 https://issues.asterisk.org/view.php?id=18421#c129310 
---------------------------------------------------------------------- 
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-12-04 20:37 pabelanger     Note Added: 0129310                          
======================================================================