From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-23767-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 11845 invoked by alias); 31 Oct 2002 22:36:01 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 11828 invoked by uid 71); 31 Oct 2002 22:36:01 -0000
Date: Thu, 31 Oct 2002 14:36:00 -0000
Message-ID: <20021031223601.11826.qmail@sources.redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
From: Joe Buck <jbuck@synopsys.com>
Subject: Re: c/8411: Segmentation fault error in malloc
Reply-To: Joe Buck <jbuck@synopsys.com>
X-SW-Source: 2002-10/txt/msg01373.txt.bz2
List-Id: <gcc-prs.sourceware.org>

The following reply was made to PR c/8411; it has been noted by GNATS.

From: Joe Buck <jbuck@synopsys.com>
To: gcc-gnats@gcc.gnu.org, bridean@ureach.com, gcc-bugs@gcc.gnu.org
Cc:  
Subject: Re: c/8411: Segmentation fault error in malloc
Date: Thu, 31 Oct 2002 14:33:42 -0800

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8411
 
 Have you checked this program with a memory-checking tool (electric fence,
 valgrind, purify, etc) and verified that it doesn't have any memory 
 allocation
 errors (e.g. double-frees, writing beyond the end of an allocated 
 object, etc.).
 The most common cause of segmentation faults in malloc is this kind of 
 user error,
 and the problems tend to show up differently depending on optimization.