Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cis.ohio-state.edu!ucbvax!hplabs!nsc!pyramid!shakespyr!amirosh
From: amirosh@shakespyr.Pyramid.COM (Alex Miroshnichenko)
Newsgroups: comp.unix.wizards
Subject: Re: Making sense of a system coredump
Message-ID: <159280@pyramid.pyramid.com>
Date: 14 Jun 91 00:34:46 GMT
References: <MARTIN.91Jun13171500@slsiris.harvard.edu>
Sender: news@pyramid.pyramid.com
Reply-To: amirosh@shakespyr.Pyramid.COM (Alex Miroshnichenko)
Distribution: comp.unix.wizards
Organization: Pyramid Technologies, Mt. View, California.
Lines: 10


Normal (BSD - like Unix ) usually have either adb or crash (or both).
On SGI you may use dbx in the kernel mode :
	cd to directory with your dumps and
	dbx -k vmunix.0 vmcore.0
After that you may try "where" command in dbx to see you stack trace.
Printing kernel structures is a little bit of a hassle (I usually just dump
memory and have system header listings ready :-). 

NOTE : the first argument to a function in the stack trace is often a garbadge.