[asterisk-bugs] [Asterisk 0016689]: [patch] Crash in res_agi when trying to send application usage
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Jan 24 23:56:05 CST 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=16689
======================================================================
Reported By: bklang
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16689
Category: Resources/res_agi
Reproducibility: always
Severity: crash
Priority: normal
Status: new
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2
SVN Revision (number only!): 242606
Request Review:
======================================================================
Date Submitted: 2010-01-24 23:55 CST
Last Modified: 2010-01-24 23:56 CST
======================================================================
Summary: [patch] Crash in res_agi when trying to send
application usage
Description:
I believe this bug is related to the fact that my console documentation is
not loaded (see bug https://issues.asterisk.org/view.php?id=16688).
When sending an invalid AGI command to Asterisk, the system attempts to
return usage information for the requested application. Based on my
reading of the crash information from gdb, because the console
documentation is not loaded, the usage information is not available
(c->usage is uninitialized). On my system, this causes a segfault when it
is referenced.
I have attached output from gdb (bt; bt full; thread apply all bt full).
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-01-24 23:56 bklang Summary Crash in res_agi when
trying to send application usage => [patch] Crash in res_agi when trying to send
application usage
======================================================================
More information about the asterisk-bugs
mailing list