[asterisk-bugs] [Asterisk 0016202]: Asterisk 1.6.0.13 Asterisk crashes when running dialplan app macro on a macro that does not exist.
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Apr 15 10:29:21 CDT 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16202
======================================================================
Reported By: jsutton
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16202
Category: Applications/app_macro
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
Asterisk Version: Older 1.6.0
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-11-06 16:28 CST
Last Modified: 2010-04-15 10:29 CDT
======================================================================
Summary: Asterisk 1.6.0.13 Asterisk crashes when running
dialplan app macro on a macro that does not exist.
Description:
I see this issue running 1.6.0.13 with asterisk addons 1.6.0.3 with
realtime extensions configured. This is a problem as a typo in an extension
can cause a crash. See CLI output below.
-- Executing macro("SIP/4692538023-086383e8", "non-exist")
[Nov 6 15:13:04] WARNING[5916]: app_macro.c:239 _macro_exec: No such
context 'macro-non-exist' for macro 'non-exist'
*CLI>
Disconnected from Asterisk server
======================================================================
----------------------------------------------------------------------
(0120462) lmadsen (administrator) - 2010-04-15 10:29
https://issues.asterisk.org/view.php?id=16202#c120462
----------------------------------------------------------------------
Debugging a crash without a backtrace is going to make getting this issue
resolved nearly impossible. Please follow the instructions in
doc/backtrace.txt.
Alternatively, you can check out the updated backtrace.txt file I worked
on this morning in issue https://issues.asterisk.org/view.php?id=17190
Issue History
Date Modified Username Field Change
======================================================================
2010-04-15 10:29 lmadsen Note Added: 0120462
2010-04-15 10:29 lmadsen Status acknowledged =>
feedback
======================================================================
More information about the asterisk-bugs
mailing list