public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: rth@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/6678: [i?86] g++ 3.1 leaks memory when throwing exceptions Date: Wed, 14 May 2003 23:26:00 -0000 [thread overview] Message-ID: <20030514232601.25571.qmail@sources.redhat.com> (raw) The following reply was made to PR target/6678; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> 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
next reply other threads:[~2003-05-14 23:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-14 23:26 Dara Hazeghi [this message] 2003-05-14 23:36 Dara Hazeghi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030514232601.25571.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=rth@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).