From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25681 invoked by alias); 14 May 2003 23:26:03 -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 25587 invoked by uid 71); 14 May 2003 23:26:02 -0000 Date: Wed, 14 May 2003 23:26:00 -0000 Message-ID: <20030514232601.25571.qmail@sources.redhat.com> To: rth@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Dara Hazeghi Subject: Re: target/6678: [i?86] g++ 3.1 leaks memory when throwing exceptions Reply-To: Dara Hazeghi X-SW-Source: 2003-05/txt/msg01723.txt.bz2 List-Id: The following reply was made to PR target/6678; it has been noted by GNATS. From: Dara Hazeghi To: rth@gcc.gnu.org, caprdja@hand-gmbh.de, gcc-gnats@gcc.gnu.org Cc: Subject: Re: target/6678: [i?86] g++ 3.1 leaks memory when throwing exceptions Date: Wed, 14 May 2003 16:25:36 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=6678 Hello, what's the current status of this bug? With 3.2 and 3.3 and -mno-accumulate-outgoing-args, the program still crashes for me, but with mainline and -mno-accumulate-outgoing-args, there is no segfault or apparent memory leak. Thanks, Dara