From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5406 invoked by alias); 15 Sep 2002 18:25:49 -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 5386 invoked by uid 61); 15 Sep 2002 18:25:49 -0000 Date: Sun, 15 Sep 2002 11:25:00 -0000 Message-ID: <20020915182549.5385.qmail@sources.redhat.com> To: flatmax@ieee.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: nathan@gcc.gnu.org Reply-To: nathan@gcc.gnu.org, flatmax@ieee.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/6216: seg fault when using new to create a memory array X-SW-Source: 2002-09/txt/msg00401.txt.bz2 List-Id: Synopsis: seg fault when using new to create a memory array State-Changed-From-To: open->feedback State-Changed-By: nathan State-Changed-When: Sun Sep 15 11:25:48 2002 State-Changed-Why: I can't copmpile this with the current CVS, because the header's no longer match the library. However, the symptoms you describe sound stunningly like you have an allocation problem. You are either writing off the end of a malloc'd array, or using a pointer after it's been freed. Try with a debugging malloc library, http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6216