From owner-freebsd-ports Fri Oct 3 00:37:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27754 for ports-outgoing; Fri, 3 Oct 1997 00:37:00 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27730; Fri, 3 Oct 1997 00:36:53 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id AAA12977; Fri, 3 Oct 1997 00:35:48 -0700 (PDT) Date: Fri, 3 Oct 1997 00:35:48 -0700 (PDT) Message-Id: <199710030735.AAA12977@silvia.HIP.Berkeley.EDU> To: Matthew.Thyer@dsto.defence.gov.au CC: freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG In-reply-to: <34348712.F0962930@dsto.defence.gov.au> (message from Matthew Thyer on Fri, 03 Oct 1997 15:18:02 +0930) Subject: Re: xlock: caught signal 8 while running galaxy mode. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * "xlock: caught signal 8 while running galaxy mode." * * Signal 8 appears to be a floating point exception (FPE) according to * kill -l. A lot of xscreensaver programs die with this too. Is this one of those "our FP exception model is absolutely correct but different from every other system" things? Satoshi