From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17762 invoked by alias); 18 Dec 2002 06:26: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 17748 invoked by uid 71); 18 Dec 2002 06:26:02 -0000 Date: Tue, 17 Dec 2002 22:26:00 -0000 Message-ID: <20021218062602.17747.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: 2002-12/txt/msg00910.txt.bz2 List-Id: The following reply was made to PR other/8822; it has been noted by GNATS. From: "Dieter Ferdinand" To: ehrhardt@mathematik.uni-ulm.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: Wed, 18 Dec 2002 07:22:24 +1 hello, i make some more tests and since i have run memtest over some hours, it seems, that on ram-module makes problems, which is not located by memtest. after i am sure, that all ram-modules are ok, i compiled gcc with the 2.2.16er kernel in single- cpu-mode. after re-compiling of all needed programms and the kernels 2.4.20 and 2.2.23, i boot the system with kernel 2.4.20 in smp-mode with 2 cpu's. i start again the compilation of gcc 3.2.1 and it breaks again with internel error and segmentation fault. i will try to compile gcc without threading, to see what happens. goodby Datum: 5 Dec 2002 17:17:25 -0000 An: dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Von: ehrhardt@mathematik.uni-ulm.de Antwort an: ehrhardt@mathematik.uni-ulm.de, 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: open->feedback > State-Changed-By: cae > State-Changed-When: Thu Dec 5 09:17:22 2002 > State-Changed-Why: > This is most likely a hardware problem with your machine. Try to run memtest > and try to replace your RAM chips. To do anything useful with this > report we'll need a preprocessed source file that reproducible causes the > compiler to crash on your machine. > > 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, ...