Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!pt.cs.cmu.edu!sei!sei.cmu.edu!pdb
From: pdb@sei.cmu.edu (Patrick Barron)
Newsgroups: comp.unix.questions
Subject: Re: Wanted:   Crash Dump Analysis Tips
Message-ID: <1410@aw.sei.cmu.edu>
Date: Sun, 24-May-87 01:50:48 EDT
Article-I.D.: aw.1410
Posted: Sun May 24 01:50:48 1987
Date-Received: Sat, 6-Jun-87 12:46:28 EDT
References: <680@umt.UUCP>
Sender: netnews@sei.cmu.edu
Reply-To: pdb@sei.cmu.edu (Pat Barron)
Organization: Carnegie-Mellon University, SEI, Pgh, Pa
Lines: 21
Keywords: VAX 11/785   -   Ultrix 1.2

In article <680@umt.UUCP> marsh@umt.UUCP (Paul Marsh) writes:
> [...]  Has anyone compiled any information that would
>help in looking through a crash dump?
> [...]  Is there any information that
>details the possible causes of the various "panics:"?  Thanks in advance.

Assuming you've loaded /usr/doc on to your system from the distribution and
uncompressed it, look in /usr/doc/kdebug, which contains a paper called
"Using ADB to Debug the Unix Kernel" (or words to that effect).  It has a
few helpful hints (probably the most useful is that doing *(scb-4)$c while
ADBing a crash dump will give you a stack traceback of what was running at
the time of the crash).  I don't think this paper is in the hardcopy document-
ation set for Ultrix, but I could be wrong.

A very few of the possible panics are detailed in the man page for crash(8).
However, that's just the tip of the iceberg - there are really more possible
panics that you'd want to think about.  If you've got a particular panic you're
curious about, the best thing to do is look around in the sources (assuming
you've got them) and find out where that panic is generated.

--Pat.