*BSD News Article 43339


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!agate!dog.ee.lbl.gov!news.cs.utah.edu!cs.utexas.edu!uwm.edu!news.alpha.net!news.mathworks.com!newshost.marcam.com!uunet!nctuccca.edu.tw!news.cc.nctu.edu.tw!news!gate!taob
From: taob@gate.sinica.edu.tw (Brian Tao)
Newsgroups: comp.os.386bsd.questions
Subject: Re: top evokes floating point exception
Date: 4 Mar 1995 09:43:09 GMT
Organization: Computing Center, Academia Sinica
Lines: 11
Message-ID: <3j9cnd$96b@gate.sinica.edu.tw>
References: <D4vw4p.4Bu@luva.lb.bawue.de>
NNTP-Posting-Host: taob%@gate.sinica.edu.tw
X-Newsreader: TIN [version 1.2 PL2]

Michael Giegerich (migieger@luva.lb.bawue.de) wrote:
:
: Strangely systat can run forever (well to the next shutdown)
: without evoking this error but once top has crashed, systat 
: too returns a floating point exception (I believe both pro-
: grams have a lot of common syscalls?).

    I can get systat from the 950210 snapshot to crash with a floating
point exception after only a few minutes if I set it to update VM stats
once a second.  Haven't seen top crash yet (but I haven't been running
it for several days straight).