Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!milton!gichan@blake.u.washington.edu
From: gichan@blake.u.washington.edu (Gilbert Chan)
Newsgroups: comp.sys.att
Subject: SIGEMT: What does it mean?
Message-ID: <18167@milton.u.washington.edu>
Date: 11 Mar 91 08:38:33 GMT
Sender: news@milton.u.washington.edu
Followup-To: bchan@ddn-eur.ddn.mil
Organization: University of Washington, Seattle
Lines: 14


I'm posting this for a friend. Please send your response
to him at bchan@ddn-eur.ddn.mil. Thank you - GC

--------------------------------------------------
I'm getting a core dump on a SIGEMT signal. The same piece 
of code has run fine on a Sun and pcs. But when I move it
to a  3B2, it bombs with a SIGEMT. I know this sig is caused
by an implementation dependent harware fault but what does 
it mean for the 3B2s?

Thank you very much for you help in advance,

Brian