BIND 10 #1008: missing initLogger() should be caught more explicitly

[BIND 10 Development]

#1008: missing initLogger() should be caught more explicitly
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  Next-
           Component:  logging       |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Yesterday I encountered an infinite loop in the unittests for
 lib/datasrc.  After struggling with it for an hour or so, I found it
 was due to missing initialization of the logging system (by calling
 initLogger()), and fixed it in commit 1302962.  (The loop occurred
 within liblog4cplus).

 But I think we should catch such a condition more explicitly with an
 assert() or an exception, because it'll happen again quite easily,
 and, when it happens it's quite difficult to identify.  Note also that
 an infinite loop in unittest is very bad for the autobuilder.

 I suggest this for the next sprint item.

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