| Summary: | ASTERISK-21111: segfault Asterisk 1.6.0.9 | ||
| Reporter: | Rustem (metsyr) | Labels: | |
| Date Opened: | 2013-02-15 03:27:33.000-0600 | Date Closed: | 2013-02-15 07:21:50.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | . I did not set the category correctly. |
| Versions: | Frequency of Occurrence | Occasional | |
| Related Issues: | |||
| Environment: | Asterisk 1.6.0.9 Linux sw 3.0.51-0.7.9-default #1 SMP Thu Nov 29 22:12:17 UTC 2012 (f3be9d0) x86_64 x86_64 x86_64 GNU/Linux Novell SUSE linux ENTEPRISE 11 (64 bit) | Attachments: | ( 0) backtrace16-54.txt ( 1) backtrace17-28.txt ( 2) load_module.txt |
| Description: | Good day, we have the following problem, we use a version of Asterisk 1.6.0.9.
periodically, Asterisk has a segfault error out without any apparent reason. Could you help to understand what is happening. Thank you. Feb 12 17:28:03 sw kernel: [638740.811506] asterisk[8275]: segfault at 0 ip 000000000041a3e0 sp 00007fe96ce22d28 error 6 in asterisk[400000+150000] | ||
| Comments: | By: Michael L. Young (elguero) 2013-02-15 07:21:34.558-0600 Maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch or 11 branch which are long term support (LTS) branches. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions. After testing with Asterisk 1.8 or 11, if you find this problem has not been resolved, please open a new issue against the supported version of Asterisk. By: Matt Jordan (mjordan) 2013-02-15 07:21:57.564-0600 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions. After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8. | ||