From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22701 invoked by alias); 16 Feb 2003 22:07:37 -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 22682 invoked by uid 48); 16 Feb 2003 22:07:37 -0000 Date: Sun, 16 Feb 2003 22:07:00 -0000 Message-ID: <20030216220737.22681.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, thyng2k@hotmail.com From: ebotcazou@gcc.gnu.org Reply-To: ebotcazou@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, thyng2k@hotmail.com, gcc-gnats@gcc.gnu.org Subject: Re: c/9720: segmentation fault compiling allegro X-SW-Source: 2003-02/txt/msg00706.txt.bz2 List-Id: Synopsis: segmentation fault compiling allegro State-Changed-From-To: open->feedback State-Changed-By: ebotcazou State-Changed-When: Sun Feb 16 22:07:37 2003 State-Changed-Why: Is the problem reproducible, i.e does the compiler crash at the very same point if you restart the build? I experienced this sort of problem while building Allegro with the same configuration as yours on one box, but had no problems at all on another one. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9720