From owner-freebsd-ports  Wed May 21 00:30:04 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA24800
          for ports-outgoing; Wed, 21 May 1997 00:30:04 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA24789;
          Wed, 21 May 1997 00:30:02 -0700 (PDT)
Date: Wed, 21 May 1997 00:30:02 -0700 (PDT)
Message-Id: <199705210730.AAA24789@hub.freebsd.org>
To: freebsd-ports
Cc: 
From: j@uriah.heep.sax.de (J Wunsch)
Subject: Re: ports/3640: xlockmore galaxy bombs out
Reply-To: j@uriah.heep.sax.de (J Wunsch)
Sender: owner-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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

From: j@uriah.heep.sax.de (J Wunsch)
To: adam@veda.is
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: ports/3640: xlockmore galaxy bombs out
Date: Wed, 21 May 1997 08:51:55 +0200

 As Adam David wrote:
 
 > 	After awhile running "galaxy mode" the program bombs out with an FPE.
 
 Known problem, i think.  This PR belongs into category `kern', or
 maybe `bin'.  Our FPU error handling is still not even remotely IEEE
 compliant.
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)