[asterisk-bugs] [Asterisk 0017050]: channel.c:2753 __ast_read: Exception flag set on 'SIP/XXXXXXXX-000000e3', but no exception handler
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jul 15 09:29:01 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17050
======================================================================
Reported By: hamidbilal
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17050
Category: Applications/app_dial
Reproducibility: sometimes
Severity: crash
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.2.6
JIRA: SWP-1105
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-17 11:02 CDT
Last Modified: 2010-07-15 09:29 CDT
======================================================================
Summary: channel.c:2753 __ast_read: Exception flag set on
'SIP/XXXXXXXX-000000e3', but no exception handler
Description:
Hi All!
We are using asterisk 1.6.2 but asterisk get crashed very often. We start
receiving error
channel.c:2753 __ast_read: Exception flag set on 'SIP/XXXXXXXX-000000e3',
but no exception handler
Then asterisk get restart automatically. Dial plan is very simple and it
also include our own developed application whcich make simple querys to
mysql db.
Please suggest us solution. I have also attached gdb output.
======================================================================
----------------------------------------------------------------------
(0124572) lmadsen (administrator) - 2010-07-15 09:29
https://issues.asterisk.org/view.php?id=17050#c124572
----------------------------------------------------------------------
Console output just prior to the crash may also be helpful. Be sure your
Asterisk is compiled with DONT_OPTIMIZE in order to produce a useful
backtrace.
---
Thank you for your bug report. In order to move your issue forward, we
require a backtrace from the core file produced after the crash. Please see
the doc/backtrace.txt file in your Asterisk source directory.
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 instructions in
doc/backtrace.txt.
When complete, attach that file to this issue report. Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2010-07-15 09:29 lmadsen Note Added: 0124572
======================================================================
More information about the asterisk-bugs
mailing list