BIND 10 #3025: Segmentation fault in SegmentObjectHolderTest.grow test

[BIND 10 Development]

#3025: Segmentation fault in SegmentObjectHolderTest.grow test
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by stephen):

 Yes.

 As indicating in the traceback (and confirmed by gdb), the line causing
 the error is in src/lib/util/memory_segment_mapped.cc in the method
 clearNamedAddressImpl().
 {{{
     return (impl_->base_sgmt_->destroy<offset_ptr<void> >(name));
 }}}
 (I'm not sure that you can believe the line in the traceback at !#11 (this
 = 0x1); this appears to be an artifact of the printing of addresses - I've
 noticed that outputting a pointer to an object comes up with "1" a number
 of times.)

 My tests show that in the test, the !MemorySegmentGrown exception in
 MemorySegmentMapped::allocate is thrown when the "size" argument is 32768.
 impl_->base_sgmt_-_get_size() returns 65536 and impl_->base_sgmt_-
 _get_free_memory() returns 65272.

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