BIND 10 #1698: log initialization causes real fiasco for MacOS 10.7

[BIND 10 Development]

#1698: log initialization causes real fiasco for MacOS 10.7
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:         |             Milestone:
  defect                             |  Sprint-20120320
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  Core
  logging                            |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by stephen):

 > In fact, when I first hit this I tried to just use a proxy for the
 "logger" object, and then find it crashed in the !MessageInitializer
 initializer.

 As I don't have a Lion system on which to test, I've committed a possible
 solution to trac1698-test.  The solution:
  * Stores the name passed to the Logger constructor in a pre-declared char
 array.
  * Stores a pointer to the array of messages passed to each
 !MessageInitializer in another (pre-declared) array.  The message IDs are
 loaded into the global dictionary once main() starts executing.

 This should avoid use of heap storage during the execution of the
 constructors of statically-initialised objects, something seems to be the
 cause of the problem.

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