public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Dieter Ferdinand" <dieter.ferdinand@gmx.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/8822: internal error segmentation fault
Date: Tue, 17 Dec 2002 22:26:00 -0000	[thread overview]
Message-ID: <20021218062602.17747.qmail@sources.redhat.com> (raw)

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

From: "Dieter Ferdinand" <dieter.ferdinand@gmx.de>
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, ...
 


             reply	other threads:[~2002-12-18  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 22:26 Dieter Ferdinand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-21 19:46 Dieter Ferdinand
2003-03-15 18:49 bangerth
2003-01-11 17:06 Labbé Stéphane
2002-12-05  9:17 ehrhardt
2002-12-05  7:06 dieter.ferdinand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021218062602.17747.qmail@sources.redhat.com \
    --to=dieter.ferdinand@gmx.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).