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 vorner):

 Replying to [comment:3 jinmei]:
 > 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.

 Throwing something that is not caught would cause the abort in the end
 anyway (at least with gcc, an uncaught exception is handled above main()
 by calling abort()). And we could be able to catch it by accident, with
 some `catch (std::exception)` or `catch (...)`. What is the benefit of
 using an exception instead of abort?

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