BIND 10 #957: IntervalTimerTest.destructIntervalTimer segfaults

BIND 10 Development do-not-reply at isc.org
Thu Jun 2 21:46:03 UTC 2011


#957: IntervalTimerTest.destructIntervalTimer segfaults
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  y-aharen                           |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20110614
                   Priority:  major  |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  0.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [ticket:957 y-aharen]:

 Quick initial check: there doesn't seem to be any change in the tests.

 Normally we should first add a test case that could trigger the bug
 without the proposed fix, fix the problem in the main code, and then
 confirm the fix actually solves the problem with the previously added
 test.

 Isn't it possible in this case?

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


More information about the bind10-tickets mailing list