Memory allocators / STL

[Loren James Rittle]

> Configured with: /home/pm/sw/gcc-3.0-cvs/gcc/configure
> --prefix=/usr/local/gcc-3 .0-cvs --enable-languages=c++ :
> (reconfigured) /home/pm/sw/gcc-3.0-cvs/gcc/configure
> --prefix=/usr/local/gcc-3.0-cvs --enable-languages=c++ :
> (reconfigured) /home/pm/sw/gcc-3.0-cvs/gcc/configure
> --prefix=/usr/local/gcc-3.0-cvs --enable-languages=c++ :
> (reconfigured) /home/pm/sw/gcc-3.0-cvs/gcc/configure
> --prefix=/usr/local/gcc-3.0-cvs --enable-languages=c++ : (reconfigured) :
> (reconfigured) /home/pm/sw/gcc-3.0-cvs/gcc/configure
> --prefix=/usr/local/gcc-3.0-cvs --enable-languages=c++
> --enable-threads

How was this compiler and library built?  It was clearly not
bootstrapped in one fell swoop.  In fact, it look likes only the last
reconfiguration has threads enabled properly.  Did you perchance, do a
bootstrap then reconfigure and then somehow only rebuild the gcc driver?

Did you skip any back traces in the report you sent?  It is missing
all the mutex locking on the allocate() calls.  Yikes.

If you don't know how that compiler was built.  Please rebootstrap
from complete scratch and try again.  It sure looks to me like something
weird happened to your build.

Regards,
Loren