Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ucbvax.UUCP
Path: utzoo!linus!decvax!tektronix!ucbcad!ucbvax!sam
From: sam@ucbvax.UUCP
Newsgroups: net.unix-wizards
Subject: Re: 4.2 crashes
Message-ID: <160@ucbvax.UUCP>
Date: Sat, 29-Oct-83 21:30:27 EST
Article-I.D.: ucbvax.160
Posted: Sat Oct 29 21:30:27 1983
Date-Received: Fri, 11-Nov-83 21:33:19 EST
References: <12965@sri-arpa.UUCP>, <1127@uwvax.ARPA>
Organization: U.C. Berkeley
Lines: 20

I have spoken to a number of people running 4.2 and none
have experienced the problem mentioned, nor have any bug
reports been mailed to Berkeley regarding such a problem
(I'm no longer there to get phone calls, so I wouldn't know
if you called).  Since you presumably have a crash dump,
you should be able to at least give more information than
it crashes with a trap 8/9 and/or lots of dz's hang.  Even
differentiating between trap type 8 and 9 would be useful.
It is almost always a simple matter to get a stack trace
from a crash dump.  Try the following after your system
reboots and savecore has recorded the dump;
	% cd /usr/crash		(or similar)
	% adb -k vmunix.XX vmcore.XX
	....
	*(scb-4)$c
This should give you a stack trace.  If it doesn't, then
you have to search for the stack frame on the interrupt or
system stack (there should always be a recognizable frame
on the interrupt stack if a dump was performed); once again
not too difficult, but more than I care to discuss here.