Xref: utzoo comp.unix.microport:3061 comp.unix.questions:12539
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcsvax!ucsdhub!hp-sdd!sceard!mrm
From: mrm@sceard.UUCP (M.R.Murphy)
Newsgroups: comp.unix.microport,comp.unix.questions
Subject: Re: C bug causes double fault
Message-ID: <885@sceard.UUCP>
Date: 30 Mar 89 02:16:17 GMT
References: <244@tree.UUCP> <9884@smoke.BRL.MIL> <27245@cci632.UUCP> <9900@smoke.BRL.MIL> <660@micropen>
Reply-To: mrm@sceard.UUCP (0040-M.R.Murphy)
Organization: Sceard Systems, Inc.  San Marcos, CA  92069
Lines: 14

In article <660@micropen> dave@micropen (David F. Carlson) writes:
!
!The truth is that Microport early versions had the potential to corrupt the
!kernel stack on floating point exceptions, which is what this should be.
!This was supposedly fixed several versions ago and I never had saw this
!again.  (It was a showstopper though for a multi-user development machine:
!too insecure to use.)
!
The program as written doesn't double panic uPort V/AT 2.2.2 with 80287,
or 2.3, 2.4 without 80287. With other combinations, your mileage may vary:-)
Which, incidentally, points out one of the large problems in getting the
bugs out of an operating system which is expected to run in who-knows-how
many hardware configurations (CPU,motherboard,disk controller,disk drive,
and on and on...). The hardware used in this exhaustive test was no-name clone.
--
Mike Murphy  Sceard Systems, Inc.  544 South Pacific St. San Marcos, CA  92069
mrm@sceard.UUCP       {hp-sdd,nosc,ucsd}!sceard!mrm            +1 619 471 0655