GKN%OAK.SAINET.MFENET@LLL-MFE.ARPA (02/09/86)
Date: Sat, 8-FEB-1986 16:40 EST
To: Info-VAX@SRI-KL.Arpa
Message-ID: <[OAK.SAINET.MFENET].86D7D380.008EA40B.GKN>
US-Mail: Science Applications; P.O. Box 2501; Oak Ridge, TN 37831
Telephone: (615) 482-9031 x293
X-VMS-Mail-To: ARPA%"Info-VAX@SRI-KL.Arpa"
From: Arpa%"ESC1111%DDAESA10.BITNET@WISCVM.WISC.EDU" 8-FEB-1986 16:13
Subj: abort tracing
Date: Thu, 06 Feb 86 10:37:41 cet
ref: John Loyd<40:jl@dac.triumf.cdn> & Dave Barrach of 3 Jan
Both of the above messages were to do with either getting dumps or
tracebacks when tasks blow up. I have desires in the same direction but
they run something like this:
- when a dies it should dump its memory map contents to disk somewhere
- it should be possible to get the dump data back in and crunch it
with the debugger!!!!! to see what went wrong
Anyone got any suggestions????
$ Run/Dump PROGRAM
$ Analyze/Process_Dump PROGRAM
gkn