Date: Fri, 03 Oct 1997 15:18:02 +0930 From: Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au> To: freebsd-current@freebsd.org, ports@freebsd.org Subject: xlock: caught signal 8 while running galaxy mode. Message-ID: <34348712.F0962930@dsto.defence.gov.au>
next in thread | raw e-mail | index | archive | help
Does anyone else have this problem or can anyone confirm that it will be solved by a newer incarnation of -CURRENT or a newer xlockmore ? I run xlockmore-4.02 on a somewhat dated FreeBSD 3.0-CURRENT now (3.0-970618-SNAP). I always use the galaxy mode for screen locking (because I love it!) and it often dies with the following error in my .xsession-errors file: "xlock: caught signal 8 while running galaxy mode." Signal 8 appears to be a floating point exception (FPE) according to kill -l. I'm finding I can't rely on the screen being locked when I leave my office. Could this be a Pentium FPU bug ?? Dmesg output for my CPU: CPU: Pentium (99.72-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8> I will get around to updating my -CURRENT soon (maybe not that soon given the recent instabilities with NFS client) and my installed ports. (I've got to work out the socks support for cvsup first before I can keep my ports collection up to date easily). Please reply directly as this address is not subscribed to the current list. -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34348712.F0962930>