[asterisk-bugs] [Asterisk 0012113]: [patch] asterisk crash at reload chan_misdn.so
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Aug 17 11:35:26 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=12113
======================================================================
Reported By: agupta
Assigned To: jpeeler
======================================================================
Project: Asterisk
Issue ID: 12113
Category: Channels/chan_misdn
Reproducibility: sometimes
Severity: crash
Priority: normal
Status: assigned
Asterisk Version: 1.4.18
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-03-01 04:46 CST
Last Modified: 2009-08-17 11:35 CDT
======================================================================
Summary: [patch] asterisk crash at reload chan_misdn.so
Description:
Program terminated with signal 11, Segmentation fault.
https://issues.asterisk.org/view.php?id=0 0x08072612 in __ast_free_region
(ptr=0x89ed6d8, file=0x813f573
"indications.c", lineno=438, func=0x813f7b7 "free_zone")
at astmm.c:152
152 for (reg = regions[hash]; reg; reg = reg->next) {
BT full is attached .
======================================================================
----------------------------------------------------------------------
(0109135) svnbot (reporter) - 2009-08-17 11:35
https://issues.asterisk.org/view.php?id=12113#c109135
----------------------------------------------------------------------
Repository: asterisk
Revision: 212498
U branches/1.4/channels/misdn_config.c
------------------------------------------------------------------------
r212498 | jpeeler | 2009-08-17 11:35:25 -0500 (Mon, 17 Aug 2009) | 12
lines
Fix segfault when reloading chan_misdn.
If more ports were specified than configured in misdn.conf a reload would
crash
asterisk. The problem was the unconfigured port was using data from the
previously configured port. When the data for an unconfigured port was
freed a
crash would result from the double free.
(closes issue https://issues.asterisk.org/view.php?id=12113)
Reported by: agupta
Patches:
bug12113.patch uploaded by jpeeler (license 325)
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=212498
Issue History
Date Modified Username Field Change
======================================================================
2009-08-17 11:35 svnbot Note Added: 0109135
======================================================================
More information about the asterisk-bugs
mailing list