[asterisk-bugs] [Asterisk 0015899]: crash on second 'dahdi destroy channel' if a var was set
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 6 14:28:15 CDT 2009
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=15899
======================================================================
Reported By: tzafrir
Assigned To: jpeeler
======================================================================
Project: Asterisk
Issue ID: 15899
Category: Channels/chan_dahdi
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 218464
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2009-09-15 06:19 CDT
Last Modified: 2009-10-06 14:28 CDT
======================================================================
Summary: crash on second 'dahdi destroy channel' if a var was
set
Description:
dell*CLI> dahdi destroy channel 1
dell*CLI> dahdi destroy channel 2
dell*CLI>
Disconnected from Asterisk server
Executing last minute cleanups
Asterisk ending (0).
It will crash this way if any variable was set in chan_dahdi.conf using
setvar.
This is because of the following in chan_dahdi.c:11259 (function mkintf)
if (conf->chan.vars) {
tmp->vars = conf->chan.vars;
}
conf->chan.vars is thus common to all channels.
Fix should be to copy each variable seperately.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-10-06 14:28 svnbot Status acknowledged =>
assigned
2009-10-06 14:28 svnbot Assigned To => jpeeler
2009-10-06 14:28 svnbot Status assigned => resolved
2009-10-06 14:28 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list