This is the mail archive of the
mailing list for the GCC project.
RE: libstd++ Memory leak under multithreaded application ?
- To: "'Benjamin Kosnik'" <bkoz at cygnus dot com>, gcc at gcc dot gnu dot org
- Subject: RE: libstd++ Memory leak under multithreaded application ?
- From: "Beardsley, Jason" <jbeardsley at origin dot ea dot com>
- Date: Wed, 17 Nov 1999 16:05:19 -0600
Here's a test case:
It still breaks with gcc-2.95.2, Solaris 7, on an SMP box.
From: Benjamin Kosnik [mailto:firstname.lastname@example.org]
Sent: Wednesday, November 17, 1999 12:56 PM
Subject: Re: libstd++ Memory leak under multithreaded application ?
I am aware of vague reports of problems with the default allocator and
MT-safe code. This is one of the reasons that v-3 has __USE_MALLOC
put this in stl/bits/stl_config.h:
# define __USE_MALLOC // As the "underlying allocator"
(And then there were these examples proving things... well I
do not have a simple test-case but I guess I could take the time to
write one if it is desireable.)
If this is ever to be fixed, somebody will have to have a
testcase. Your efforts towards this end would be appreciated.