mt_allocator: static DE-initialization order fiasco?

[Paolo Carlini]

Carlo Wood wrote:

>The static initialization order fiasco is wellknown, but
>something similar can occur when global or static objects
>are being destructed.
>
>In the current CVS HEAD, the default implementation of
>the STL allocator (mt_alloc) is using static objects
>for the memory pool instances.  When these instances
>are being destructed they delete the memory that is
>still in use by the pool.
>  
>
To be sure: are you using the latest src/mt_allocator.cc, version 1.4??

In any case, a small testcase would help...

Paolo.