[asterisk-bugs] [Asterisk 0012113]: [patch] asterisk crash at reload chan_misdn.so

[Asterisk Bug Tracker]

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-12 13:55 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 .
====================================================================== 

---------------------------------------------------------------------- 
 (0108963) jpeeler (administrator) - 2009-08-12 13:55
 https://issues.asterisk.org/view.php?id=12113#c108963 
---------------------------------------------------------------------- 
This bug appears to be complicated by the usage of safe_asterisk and
possibly crashing before the given backtraces occurred. The only way I
could get a crash was to specify more ports than were configured and then
try reloading the module. Attached is the patch that solves this problem.
If the issue is still not fixed, providing your misdn.conf file will be
necessary. I'm using mISDN 1.1.9.1 as building the older releases require
patching for modern kernels. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-12 13:55 jpeeler        Note Added: 0108963                          
======================================================================