From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12226 invoked by alias); 15 May 2002 14:42:36 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 12150 invoked by uid 61); 15 May 2002 14:42:34 -0000 Date: Wed, 15 May 2002 07:42:00 -0000 Message-ID: <20020515144234.12149.qmail@sources.redhat.com> To: bkoz@gcc.gnu.org, gawrilow@math.tu-berlin.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: bkoz@gcc.gnu.org Reply-To: bkoz@gcc.gnu.org, bkoz@gcc.gnu.org, gawrilow@math.tu-berlin.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/6582: memory leaks in iostream and locale X-SW-Source: 2002-05/txt/msg00423.txt.bz2 List-Id: Synopsis: memory leaks in iostream and locale Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Wed May 15 07:42:33 2002 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: bkoz State-Changed-When: Wed May 15 07:42:33 2002 State-Changed-Why: Please consider using the soon-to-be released 3.1.0, or mainline 3.2 sources. Both have revamped allocation strategies from the code you are using, and neither have the problems you are reporting. I've checked with valgrind and the current sources, and everything looks ok except for one issue with the underlying "C" locale information, which valgrind displays as a 16 and a 64 byte leak. These are to be expected. Before the allocation tuning happened, there were 53 such issues. -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6582