From owner-freebsd-stable Wed Oct 14 14:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27647 for freebsd-stable-outgoing; Wed, 14 Oct 1998 14:23:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27640 for ; Wed, 14 Oct 1998 14:23:43 -0700 (PDT) (envelope-from peter.jeremy@AUSS2.ALCATEL.COM.AU) Received: by border.alcanet.com.au id <40332>; Thu, 15 Oct 1998 07:22:47 +1000 Date: Thu, 15 Oct 1998 07:23:18 +1000 From: Peter Jeremy Subject: Re: got SIGFPE exception from xlock To: freebsd-stable@FreeBSD.ORG Message-Id: <98Oct15.072247est.40332@border.alcanet.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Karlsson wrote: >At Wed, 14 Oct 1998 11:12:21 +0800, Wilson Tam wrote: >>I am using 2.2.7 on a K6 machine. I got a problem on xlock, it generates >>SIGFPE exception once awhile. I have also seen this. It is a bug in xlock. >This does not belong to this list, but since I do not know where it should be >I will reply only to this list. The logical place would seem to be xlock@tux.org, or the maintainer: David A. Bagley >I have also had this problem and narrowed it down to the mode named "discrete" >I does not appear every time but is reprodusable. I think I've seen it in a couple of different modes in xlockmode-4.07, but don't have a record of them to hand. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message