| Summary: | ASTERISK-11536: Asterisk Segmentation Fault - High fence violation in ast_frdup of frame.c | ||
| Reporter: | py (py) | Labels: | |
| Date Opened: | 2008-02-28 07:02:01.000-0600 | Date Closed: | 2011-06-07 14:00:43 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) gdb.txt ( 1) malloc_debug.txt ( 2) valgrind.txt | |
| 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 ****** ADDITIONAL INFORMATION ****** OS: CentOS5 i386 Asterisk 1.4.18 Zaptel 1.4.9 Freepbx 2.4.0.0 Spandsp 0.0.4pre16 Will attach malloc.txt and valgrind.txt separately. | ||
| Comments: | By: py (py) 2008-02-28 07:22:20.000-0600 I executed gdb /usr/sbin/asterisk (gdb) r -U asterisk -G asterisk -vvvvcg Then punch the fax extension, with freepbx configurations, segfaulted and obtained the Gdb bt full. I attached it with some callerid info censored. Strange though it points to places other than frame.c. By: Tilghman Lesher (tilghman) 2008-02-28 08:34:55.000-0600 app_rxfax is not distributed with Asterisk and is thus not supported here. Please take this up with the distributor of that module. | ||