| Summary: | ASTERISK-28450: Program terminated with signal 11, Segmentation fault at t38_gateway.c:2189 | ||||
| Reporter: | Andrew McRory (amace) | Labels: | fax | ||
| Date Opened: | 2019-06-13 11:34:47 | Date Closed: | 2019-06-17 05:13:24 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_fax_spandsp | ||
| Versions: | 13.23.1 13.25.0 13.26.0 13.27.0 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | KVM OS: CentOS release 6.10 (Final) running in OpenVZ container on Proxmox 2.3-13 (Kernel 2.6.32-19-pve) asterisk-13.21.1-2.C6.SC.x86_64 (stable version) asterisk-libpri-1.6.0-2.C6.SC.x86_64 asterisk-perl-1.03-1.C6.LSE.x86_64 dahdi-linux-3.0.0-2.6.32_754.14.2.el6.centos.plus.x86_64_2.C6.SC.x86_64 dahdi-tools-3.0.0-1.C6.SC.x86_64 dahdi-tools-libs-2.1.0.2-8.el6.x86_64 spandsp-0.0.6-0.8.pre21.el6.x86_64 spandsp-devel-0.0.6-0.8.pre21.el6.x86_64 | Attachments: | ( 0) asterisk-13.27.0-t38-segfault.txt | ||
| Description: | Upgraded a stable running system with t.38 support. Used latest version when compiling (13.27.0) and found outbound fax calls randomly segfault the system. Tried compiling earlier version and found the same issue repeatedly. Finally found 13.21.1 is stable in same environment. Backtrace supplied from core dump in 13.27.0. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2019-06-13 11:34:47.861-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Andrew McRory (amace) 2019-06-13 11:36:22.349-0500 gdb backtrace and excerpt from asterisk log | ||||