[asterisk-bugs] [Asterisk 0010125]: asterisk crashes on reloading after bindaddr is changed
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Jul 30 12:36:30 CDT 2007
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=10125
======================================================================
Reported By: makoto
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 10125
Category: Channels/chan_sip/General
Reproducibility: always
Severity: crash
Priority: normal
Status: resolved
Asterisk Version: 1.2.18
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: Yes
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 07-05-2007 20:06 CDT
Last Modified: 07-30-2007 12:36 CDT
======================================================================
Summary: asterisk crashes on reloading after bindaddr is
changed
Description:
Steps
1. Set bindaddr in sip.conf to incorrect value. (e.g. 10.0.0.0)
2. Start asterisk (not reload)
3. Set bindaddr in sip.conf to correct value. (e.g. 0.0.0.0)
4. Reload asterisk
5. Crash
sipsock_read_id is not initialized, but it is passed to ast_io_change,
then crash.
======================================================================
----------------------------------------------------------------------
file - 07-30-07 12:36
----------------------------------------------------------------------
Yes, we've probably discussed this on the -dev mailing list and stuff is
initialized to NULL.
Issue History
Date Modified Username Field Change
======================================================================
07-30-07 12:36 file Status feedback => resolved
07-30-07 12:36 file Resolution reopened => fixed
07-30-07 12:36 file Assigned To => file
07-30-07 12:36 file Note Added: 0068066
======================================================================
More information about the asterisk-bugs
mailing list