From owner-freebsd-stable Thu Nov 23 11:21:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 31A3B37B4C5 for ; Thu, 23 Nov 2000 11:21:51 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id MAA17360; Thu, 23 Nov 2000 12:21:47 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200011231921.MAA17360@freeway.dcfinc.com> Subject: Re: make world on 4.2-R breaking In-Reply-To: <000701c054cb$fbd10e10$0b6cffc8@infolink.com.br> from Antonio Carlos Pina at "Nov 22, 0 07:34:24 pm" To: apina@infolink.com.br (Antonio Carlos Pina) Date: Thu, 23 Nov 2000 12:21:47 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Antonio Carlos Pina wrote: > Let me try again ;-) Since I don't know what is "signal 4"... If you look in /usr/include/sys/signal.h, you'll see that signal 4 is caused when your CPU encounters an illegal instruction. Which would most likely be caused by memory corruption, or a faulty processor. If there =were= a software problem, it would have to be the compiler (assembler, actually) generating bad data. But many thousands of folks are using that compiler/assembler successfully, which is why folks here are suggesting it is a problem with your system. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message