Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!zib-berlin.de!news.tu-chemnitz.de!irz401!narcisa.sax.de!not-for-mail
From: j@narcisa.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Slight flame from Linux user
Date: 6 Jun 1995 11:12:54 +0200
Organization: Private U**x site, Dresden.
Lines: 27
Message-ID: <3r166m$fit@bonnie.tcd-dresden.de>
References: <3ql3gd$je2@bell.maths.tcd.ie> <3qp02d$eqb@news1.best.com> <3qpfm0$76j@bell.maths.tcd.ie>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Timothy Murphy <tim@maths.tcd.ie> wrote:
>> Fatal signal 11 syndrome is almost always a HARDWARE PROBLEM -
...
>While the general opinion (including mine) is that the problem
>is hardware-based, a minority believe it is a problem with gcc.
>[Even if it is a RAM problem, it is conceivable
>that the kernel might pick it up and correct it.]
Wow! It would be an interesting task for you to prove this statement!
Should the kernel provide ECC's for all RAM cells?
...
>Some people claim that it only occurs when using gcc 2.6.?,
>and that reverting to 2.5.8 will solve it.
>So it is conceivable that the problem might not arise with FreeBSD.
I'm surprised about your conclusion. I hope you are aware that
FreeBSD is using just the same gcc you're blaming here?
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)