[asterisk-bugs] [Asterisk 0016839]: ASterisk 1.6.0.13
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Feb 17 14:09:27 CST 2010
The following issue has been CLOSED
======================================================================
https://issues.asterisk.org/view.php?id=16839
======================================================================
Reported By: obugueno
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16839
Category: Applications/General
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: closed
Asterisk Version: Older 1.6.0 - please test a newer version
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0
SVN Revision (number only!):
Request Review:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2010-02-16 09:27 CST
Last Modified: 2010-02-17 14:09 CST
======================================================================
Summary: ASterisk 1.6.0.13
Description:
I do not write well in English but I have a bug with asterisk next, my
debian lenny distribution is smp kernel 2.6.26-2-686, 1.6.0.13 asterisk
addons 1.6.0.2:
February 16 11:35:12 CIACMAIPU01 kernel: [981351.707841] asterisk
[11,996]: segfault at 41 ip 0809580f sp asterisk b6846960 error 4 in
[8048000 +13 E000]
February 16 11:44:15 CIACMAIPU01 kernel: [981908.795711] asterisk
[14,992]: segfault at 50 ip bfff34c0 sp 081311d7 error 4 in asterisk
[8048000 +13 E000]
And to be working is because, greetings
======================================================================
----------------------------------------------------------------------
(0118184) lmadsen (administrator) - 2010-02-17 14:09
https://issues.asterisk.org/view.php?id=16839#c118184
----------------------------------------------------------------------
This is quite an old version of Asterisk you're using. If you can reproduce
with the latest version of Asterisk (ideally from the branch directly) then
please open a new issue. You will need to provide:
* console output prior to the crash with debug level logging enabled
(logger.conf)
* a backtrace of the issue, as per the doc/backtrace.txt file in your
Asterisk sources
Issue History
Date Modified Username Field Change
======================================================================
2010-02-17 14:09 lmadsen Note Added: 0118184
2010-02-17 14:09 lmadsen Status new => closed
======================================================================
More information about the asterisk-bugs
mailing list