[asterisk-bugs] [Asterisk 0015378]: [patch] Crash in do_monitor() in chan_dahdi.c

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Sep 15 11:01:22 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15378 
====================================================================== 
Reported By:                samy
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   15378
Category:                   Channels/chan_dahdi
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.13 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-06-22 12:54 CDT
Last Modified:              2009-09-15 11:01 CDT
====================================================================== 
Summary:                    [patch] Crash in do_monitor() in chan_dahdi.c
Description: 
I'm unable to reproduce but have a core file of Asterisk 1.6.0.10 of a
crash in chan_dahdi.c. It looks like `iflist` may have been modified
somewhere else without a lock though I'm not positive (see Additional
Information or attached file).

I have MALLOC_DEBUG, DONT_OPTIMIZE, DEBUG_THREADS and DEBUG_CHANNEL_LOCKS
enabled.

I'm running Asterisk 1.6.0.10 on linux:
[root ~]# cat /etc/redhat-release 
Fedora Core release 3 (Heidelberg)
[root ~]# uname -a
Linux pbxtra1063 2.6.9-1.667 https://issues.asterisk.org/view.php?id=1 Tue Nov 2
14:41:25 EST 2004 i686 i686 i386
GNU/Linux

I've attached a full backtrace. Please let me know if there is any more
info I can provide.
====================================================================== 

---------------------------------------------------------------------- 
 (0110664) svnbot (reporter) - 2009-09-15 11:01
 https://issues.asterisk.org/view.php?id=15378#c110664 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 218576

_U  branches/1.6.2/
U   branches/1.6.2/channels/chan_dahdi.c

------------------------------------------------------------------------
r218576 | jpeeler | 2009-09-15 11:01:22 -0500 (Tue, 15 Sep 2009) | 25
lines

Merged revisions 218430 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r218430 | jpeeler | 2009-09-14 17:38:25 -0500 (Mon, 14 Sep 2009) | 18
lines
  
  Merged revisions 218401 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r218401 | jpeeler | 2009-09-14 16:47:11 -0500 (Mon, 14 Sep 2009) | 11
lines
    
    Fix handling of DAHDI_EVENT_REMOVED event to prevent crash in
do_monitor.
    
    After talking to rmudgett about some of his recent iflist locking
changes, it
    was determined that the only place that would destroy a channel
without being
    explicitly to do so was in handle_init_event. The loop to walk the
interface
    list has been modified to wait to destroy the channel until the
dahdi_pvt of
    the channel to be destroyed is no longer needed.
    
    (closes issue https://issues.asterisk.org/view.php?id=15378)
    Reported by: samy
  ........
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=218576 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-15 11:01 svnbot         Checkin                                      
2009-09-15 11:01 svnbot         Note Added: 0110664                          
======================================================================




More information about the asterisk-bugs mailing list