From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31818 invoked by alias); 21 Mar 2003 19:46:02 -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 31784 invoked by uid 71); 21 Mar 2003 19:46:01 -0000 Date: Fri, 21 Mar 2003 19:46:00 -0000 Message-ID: <20030321194601.31783.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Dieter Ferdinand" Subject: Re: other/8822: internal error segmentation fault Reply-To: "Dieter Ferdinand" X-SW-Source: 2003-03/txt/msg01418.txt.bz2 List-Id: The following reply was made to PR other/8822; it has been noted by GNATS. From: "Dieter Ferdinand" To: bangerth@dealii.org, dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/8822: internal error segmentation fault Date: Fri, 21 Mar 2003 20:39:44 +1 hello, i have used a dual-processor-system with 2 p-200 to compile gcc 3.1. when i boot without smp-support, this works fine, when i boot with smp support, the compiler crash with an internal error. i test it under some different linux-versions (2.2 and 2.4) and have the same error. i can't say more to this error, i can only give you access to this system, to test it self. i can also test it on some other dual-systems, but this doen't solve the problem. how can i dealtivate the theading functions for gcc ? goodby Datum: 15 Mar 2003 18:49:42 -0000 An: dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Von: bangerth@dealii.org Antwort an: bangerth@dealii.org, dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Betreff: Re: other/8822: internal error segmentation fault > Synopsis: internal error segmentation fault > > State-Changed-From-To: feedback->closed > State-Changed-By: bangerth > State-Changed-When: Sat Mar 15 18:49:42 2003 > State-Changed-Why: > Whatever the cause may be, if we are to fix something then > we need a _reproducible_ testcase. > > At any rate, repeated sporadic errors on a widely > available system on which gcc is built daily are not > enough to describe a bug. > > W. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8822 > > Schau auch einmal auf meine Homepage (http://go.to/dieter-ferdinand). Dort findest du Information zu Linux, Novell, Win95, WinNT, ...