[asterisk-bugs] [Asterisk 0015913]: auto-loading res_snmp causes Asterisk to Seg fault

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15913 
====================================================================== 
Reported By:                jthurman
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15913
Category:                   Resources/res_snmp
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.1.6 
JIRA:                       SWP-218 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-17 17:43 CDT
Last Modified:              2010-05-04 04:28 CDT
====================================================================== 
Summary:                    auto-loading res_snmp causes Asterisk to Seg fault
Description: 
If modules.conf has autoload=yes and res_snmp.so is compiled, then Asterisk
seg faults every time.  If autoload=no or noload=> res_snmp.so the issue
goes away.  You can manually load res_snmp after the initial startup of
Asterisk with no issue.
====================================================================== 

---------------------------------------------------------------------- 
 (0121328) AlexSav (reporter) - 2010-05-04 04:28
 https://issues.asterisk.org/view.php?id=15913#c121328 
---------------------------------------------------------------------- 
auto-loading res_snmp causes Asterisk 1.6.0.21 to Seg fault on freebsd6.
this problem solved by
chgrp asterisk /dev/kmem
chgrp asterisk /dev/mem
but it may cause security risk 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-04 04:28 AlexSav        Note Added: 0121328                          
======================================================================