BIND 10 #1019: catch specific exception types for logging

[BIND 10 Development]

#1019: catch specific exception types for logging
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Continuation from closed #1018...

 We decided long ago to have unique log IDs. This log ID with
 {{{
 "RESOLVER_FAILED", "resolver failed, reason: %1"
 }}}
 generated by src/bin/resolver/main.cc
 {{{
 } catch (const std::exception& ex) {
         LOG_FATAL(resolver_logger, RESOLVER_FAILED).arg(ex.what());
 }}}
 is not unique.


 From jabber: (11:03:21) jelte: but i agree that the way we handle those
 catchalls leaves room for improvement, we should catch more specific
 exception types if we know they can happen

-- 
Ticket URL: <https://bind10.isc.org/ticket/1019>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development