From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-185919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 31754 invoked by alias); 15 May 2006 16:47:05 -0000
Received: (qmail 31729 invoked by uid 48); 15 May 2006 16:46:59 -0000
Date: Mon, 15 May 2006 16:47:00 -0000
Message-ID: <20060515164659.31728.qmail@sourceware.org>
X-Bugzilla-Reason: CC
References: <bug-27615-12688@http.gcc.gnu.org/bugzilla/>
Subject: [Bug libstdc++/27615] memory leak with  libstdc++  set <string>
In-Reply-To: <bug-27615-12688@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2006-05/txt/msg01475.txt.bz2
List-Id: <gcc-bugs.sourceware.org>



------- Comment #3 from pcarlini at suse dot de  2006-05-15 16:46 -------
Missing a self-contained, simple testcase, certainly we cannot even imagine
debugging this... Also, please use valgrind, very reliable and commonly
available.


-- 

pcarlini at suse dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27615