Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!ames!eos!shelby!msi.umn.edu!cs.umn.edu!poincare.geom.umn.edu!slevy
From: slevy@poincare.geom.umn.edu (Stuart Levy)
Newsgroups: comp.sys.mips
Subject: MIPS floating-exception/illegal instruction bug?
Summary: what was that bug again?
Message-ID: <1990Nov29.182320.24295@cs.umn.edu>
Date: 29 Nov 90 18:23:20 GMT
Sender: slevy@geom.umn.edu
Organization: Geometry Group, University of Minnesota
Lines: 17
Nntp-Posting-Host: poincare.geom.umn.edu

A few months back someone posted (on comp.sys.mips) a 3-instruction program
to cause a MIPS kernel panic.  I tried it on an Iris; it paniced their
kernel too.  It was something about a branch whose delay-slot was filled
by an illegal floating-point-type instruction, and whose target was
another such instruction, or one causing a floating exception.
I can't remember exactly, and after trying a number of combinations last night
couldn't get anything worse than an "Illegal instruction" core dump.

Anyway, I now need a way to get a crash dump from one of our Irises,
which occasionally misbehaves.  SGI customer support can't tell me any way
to do this, but I think that program might save the day.  Can anyone out
there tell me the magic recipe?

Thanks in advance,

    Stuart Levy, Geometry Group, University of Minnesota
    slevy@geom.umn.edu, (612) 624-1867