BIND 10 #957: IntervalTimerTest.destructIntervalTimer segfaults

[BIND 10 Development]

#957: IntervalTimerTest.destructIntervalTimer segfaults
-------------------------------------+-------------------------------------
            Reporter:  y-aharen      |                        Owner:
                Type:  defect        |  y-aharen
            Priority:  major         |                       Status:  new
           Component:  Unclassified  |                    Milestone:  New
           Sensitive:  0             |  Tasks
         Sub-Project:  DNS           |                     Keywords:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 http://bind10.isc.org/~tester/2011/05/20110519145655-d2ee006/make-
 coverage.out
 {{{
 [ RUN      ] IntervalTimerTest.destructIntervalTimer
 /bin/sh: line 5:  2412 Segmentation fault      ${dir}$tst
 FAIL: run_unittests
 }}}

 http://bind10.isc.org/~tester/builder//BIND10/20110510165000-NetBSD5-amd64/logs/unittests.out
 {{{
 [ RUN      ] IntervalTimerTest.destructIntervalTimer
 terminate called after throwing an instance of
 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_function_call>
 >'
   what():  call to empty boost::function
 [1]   Abort trap (core dumped) ${dir}${tst}
 FAIL: run_unittests
 }}}

 !IntervalTimerTest.destructIntervalTimer fails occasionally. These are not
 timing issue.

 deadline_timer handlers may be called after canceling the timer. To solve
 the problem, we should redesign !IntervalTimer not to delete resources
 while deadline_timer is holding the handler.

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