[bind10-dev] Bugs identified by STL debug mode (Re: Windows support)

[Shane Kerr]

Jinmei,

On Fri, 2011-04-08 at 15:28 -0700, JINMEI Tatuya / 神明達哉 wrote:
> Thanks, and this reminded me that we used stlport (with SunStudio C++
> compiler) for our Solaris buildbot, which also has a debug mode.  I
> managed to make the code buildable with that mode, and it reported at
> least the following bugs:
> 
> [ RUN      ] Rdata_Unknown_Test.createFromText
> /export/home/opt/sunstudio12.1/prod/include/CC/stlport4/stl/debug/_vector.h(129): STL error : Index out of bounds
> /export/home/opt/sunstudio12.1/prod/include/CC/stlport4/stl/debug/_vector.h(129): STL assertion failure:     __n < _Base::size()
> 
> [ RUN      ] CCSessionTest.checkCommand
> /export/home/opt/sunstudio12.1/prod/include/CC/stlport4/stl/debug/_vector.h(250): STL error : Past-the-end iterator could not be erased
> /export/home/opt/sunstudio12.1/prod/include/CC/stlport4/stl/debug/_vector.h(250): STL assertion failure:     __position._M_iterator !=this->_M_finish
> 
> [ RUN      ] ResponseScrubberTest.ScrubAllSectionsValid
> /export/home/opt/sunstudio12.1/prod/include/CC/stlport4/stl/debug/_iterator.h(157): STL assertion failure : _Incrementable(*this,1,_Iterator_category())
> 
> Since these errors made the test process abort itself, it cannot
> report other errors in the same module.  But we can at least be
> confident that all other modules than these three are bug free in
> terms of stlport checks.  I think the current quality is not so bad.

So, I guess the plan is to make tickets for these bugs? (Or one ticket
for all bugs.)

That also reminds me, running the BIND 10 Python tests in 3.2 results in
lots of warnings - mostly harmless things like "file not closed" but
these should be looked at. I've created ticket #845 for this:

http://bind10.isc.org/ticket/845

--
Shane