| Summary: | ASTERISK-14360: Crash when trying to log via ast_log | ||
| Reporter: | Samy Kamkar (samyk) | Labels: | |
| Date Opened: | 2009-06-22 13:05:53 | Date Closed: | 2009-09-24 09:16:07 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_dahdi |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) 1063cr2.txt | |
| Description: | I'm unable to reproduce but have a core file of Asterisk 1.6.0.10 of this crash. I've attached a full backtrace. I have MALLOC_DEBUG, DONT_OPTIMIZE, DEBUG_THREADS and DEBUG_CHANNEL_LOCKS enabled. I'm running Asterisk 1.6.0.10 on linux: [root ~]# cat /etc/redhat-release Fedora Core release 3 (Heidelberg) [root ~]# uname -a Linux pbxtra1063 2.6.9-1.667 #1 Tue Nov 2 14:41:25 EST 2004 i686 i686 i386 GNU/Linux Please let me know if there is any more info I can provide! | ||
| Comments: | By: Russell Bryant (russell) 2009-09-10 21:44:37 There is not enough information available in the backtrace to determine exactly where the problem is. Also, it is possible that the crash is outside of Asterisk. Given that this is an ancient and unsupported distribution, I don't think it's worth trying to dig into it to find out. I would strongly recommend using a modern and supported distribution. Lastly, I see "pbxtra" in your uname -a output. If this is actually a pbxtra system, and the patch set for pbxtra is applied, we do not support patched versions of Asterisk. | ||