From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32106 invoked by alias); 25 Mar 2010 11:40:49 -0000 Received: (qmail 32098 invoked by uid 22791); 25 Mar 2010 11:40:48 -0000 X-SWARE-Spam-Status: No, hits=-7.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 25 Mar 2010 11:40:41 +0000 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o2PBeeE4010055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 25 Mar 2010 07:40:40 -0400 Received: from zebedee.pink (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o2PBecfO030142; Thu, 25 Mar 2010 07:40:39 -0400 Message-ID: <4BAB4BB6.6080309@redhat.com> Date: Thu, 25 Mar 2010 13:58:00 -0000 From: Andrew Haley User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Re: Segmentation fault References: <1269516508.7204.9.camel@beamends-1> In-Reply-To: <1269516508.7204.9.camel@beamends-1> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2010-03/txt/msg00288.txt.bz2 On 03/25/2010 11:28 AM, beamendsltd wrote: > I'm having a problem with a program in C that I wrote and have been > using for some time. All of a sudden it has started crashing with a > segmentation fault which I cannot track down. Is the a way compiling in > some sort extra run-time options that would give a better indication of > what is causing the segmentation fault? If you're running on a GNU/Linux system, use Valgrind's memory checker. Andrew.