| Summary: | ASTERISK-23810: Crash - segfault in ast_channel_hangupcause_set | ||
| Reporter: | John Campbell (Sc00by) | Labels: | |
| Date Opened: | 2014-05-31 10:59:13 | Date Closed: | 2014-06-19 17:04:01 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 11.9.0 | Frequency of Occurrence | One Time |
| Related Issues: | |||
| Environment: | FreePBX 2.11 64bit | Attachments: | ( 0) backtrace.txt |
| Description: | Asterisk crashed unexpectedly last week but thankfully self recovered. I can't see anything in the log leading upto the crash but this was in dmsg:
asterisk[25067]: segfault at 9f0 ip 000000000049887e sp 00007f14022be760 error 6 in asterisk[400000+235000] I've never had a segfault before but curious to the cause to investigate. backtrace attached. | ||
| Comments: | By: Matt Jordan (mjordan) 2014-05-31 17:17:08.146-0500 Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. 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 backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace Unfortunately, the attached backtrace does not contain sufficient information for us to diagnose or fix the problem. If you can reproduce the problem, please generate a backtrace using the instructions on the wiki. Thanks! By: Walter Doekes (wdoekes) 2014-06-04 04:14:02.716-0500 Perhaps simply following the suggestion by gdb is enough. {quote} Missing separate debuginfos, use: debuginfo-install asterisk11-core-11.9.0-46_centos6.x86_64 {quote} .. and redo getting the backtrace. By: John Campbell (Sc00by) 2014-06-04 10:15:42.559-0500 I'll see what I can do, but as I am sure you understand, this is a live system and I don't really want to go and deliberatly crash it. However, I think I know what caused it. I have an WPU-7800 Wifi cordless phone that was still programmed to an extension. It was on my desk switched off as it was marked as faulty. THere was another WPU-7800 phone switched on and registered (it's replacement). I switched on the phone on my desk knowing that it had the profile for the already active phone and I thought I got to the factory reset section before it connected to the wireless. A spooky coincidence is that a call came through the system for that number and I think this is there the problem was. The call successfully routed to the correct phone a second after Asterisk self recovered by this time I had the one on my desk factory reset. By: Rusty Newton (rnewton) 2014-06-19 17:03:16.202-0500 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||