[asterisk-bugs] [Asterisk 0015379]: Crash when trying to log via ast_log
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Sep 10 21:44:38 CDT 2009
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=15379
======================================================================
Reported By: samy
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 15379
Category: Channels/chan_dahdi
Reproducibility: unable to reproduce
Severity: crash
Priority: normal
Status: resolved
Target Version: 1.6.0.x Pending Blocker
Asterisk Version: 1.6.0.10
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: won't fix
Fixed in Version:
======================================================================
Date Submitted: 2009-06-22 13:05 CDT
Last Modified: 2009-09-10 21:44 CDT
======================================================================
Summary: Crash when trying to log via ast_log
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 https://issues.asterisk.org/view.php?id=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!
======================================================================
----------------------------------------------------------------------
(0110547) russell (administrator) - 2009-09-10 21:44
https://issues.asterisk.org/view.php?id=15379#c110547
----------------------------------------------------------------------
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.
Issue History
Date Modified Username Field Change
======================================================================
2009-09-10 21:44 russell Note Added: 0110547
2009-09-10 21:44 russell Status new => resolved
2009-09-10 21:44 russell Resolution open => won't fix
2009-09-10 21:44 russell Assigned To => russell
======================================================================
More information about the asterisk-bugs
mailing list