Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: tadams@llex.ll.mit.edu ( Tony Adams)
Newsgroups: comp.sys.sun
Subject: Post-mortem kernel core dump
Keywords: Miscellaneous
Message-ID: <2184@brchh104.bnr.ca>
Date: 25 Mar 91 22:00:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 12
Approved: Sun-Spots@rice.edu
X-Original-Date: Sun, 24 Mar 91 23:53:26 GMT
X-Sun-Spots-Digest: Volume 10, Issue 69, message 7
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

machine: SUN 3E (SUNOS 4.03) with source code.

During post-mortem examination of kernel core dumps, what is the most user
level context, for a target process, that can be reconstructed??

Its easy to switch process context via "pid$<setproc". Then from there its
easy to determine the user level register values by following "u.u_ar0".

And  to what was in-core at the time of the dump, are there any "canned" ways
to locate and examine the target processes text, data and stack pages?

Any help is appreciated.