This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: mt_allocator: static DE-initialization order fiasco?

From: Paolo Carlini <pcarlini at suse dot de>
To: Carlo Wood <carlo at alinoe dot com>
Cc: libstdc++ at gcc dot gnu dot org
Date: Sun, 10 Oct 2004 19:05:51 +0200
Subject: Re: mt_allocator: static DE-initialization order fiasco?
References: <20041010162821.GA8496@alinoe.com>

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.

Follow-Ups:
- Re: mt_allocator: static DE-initialization order fiasco?
  - From: Carlo Wood

References:
- mt_allocator: static DE-initialization order fiasco?
  - From: Carlo Wood

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]