From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27144 invoked by alias); 19 Apr 2002 20:04:16 -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 27094 invoked by uid 61); 19 Apr 2002 20:04:12 -0000 Date: Fri, 19 Apr 2002 13:04:00 -0000 Message-ID: <20020419200412.27093.qmail@sources.redhat.com> To: allali@univ-mlv.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: pme@gcc.gnu.org Reply-To: pme@gcc.gnu.org, allali@univ-mlv.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/4164: 33 Memory Leak when using iostream X-SW-Source: 2002-04/txt/msg00989.txt.bz2 List-Id: Synopsis: 33 Memory Leak when using iostream State-Changed-From-To: open->feedback State-Changed-By: pme State-Changed-When: Fri Apr 19 13:04:10 2002 State-Changed-Why: Backtraces from a tool we don't have do not help us, especially when the backtraces do not specify /where/ the suspected memory leak takes place. Can you specify function names or line numbers? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4164