[asterisk-bugs] [Asterisk 0012097]: Asterisk Segmentation Fault - High fence violation in ast_frdup of frame.c

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=12097 
====================================================================== 
Reported By:                py
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12097
Category:                   Core-General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             02-28-2008 07:02 CST
Last Modified:              02-28-2008 08:34 CST
====================================================================== 
Summary:                    Asterisk Segmentation Fault - High fence violation
in ast_frdup of frame.c
Description: 
- After upgrading from Asterisk 1.4.1 to 1.4.18, our installation with
Freepbx and Spandsp crashes during or after RxFax, with a segmentation
fault

- When using Asterisk 1.4.18 with a one-liner extensions RxFax (i.e.
skipping all the Freepbx generated configurations), there were no seg
fault.

- When using Asterisk 1.4.1, it works fine with both Freepbx and
Spandsp/RxFax
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 02-28-08 08:34  
---------------------------------------------------------------------- 
app_rxfax is not distributed with Asterisk and is thus not supported here. 
Please take this up with the distributor of that module. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-28-08 08:34  Corydon76      Note Added: 0083110                          
02-28-08 08:34  Corydon76      Status                   new => closed       
02-28-08 08:34  Corydon76      Resolution               open => no change
required
======================================================================