BIND 10 #1850: core dump at isc::server_common::portconfig::installListenAddresses when Error while reading data from cc session

[BIND 10 Development]

#1850: core dump at isc::server_common::portconfig::installListenAddresses when
Error while reading data from cc session
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  Unclassified                       |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:2 jreed]:

 > > This is the desired behaviour I believe. This is how the thing reacts
 to not being able to close previous sockets/give them up to boss. If we
 ignored the error, the system would end up in an inconsistent state, so we
 terminate here. The problem with msgq is a separate issue. OK to close as
 invalid?
 >
 > I'd prefer not to close it yet. The system had over 800 core dumps from
 BIND 10 which used up all disk space. In that case it is not desired :)

 Terminating the process is probably okay.  Using abort() is too harsh
 though.  I'd suggesting throwing something like auth::FatalError,
 which is not expected to be caught in the middle of the process and
 should be only used for emergency (but as graceful as possible)
 termination.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1850#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development