ESC1111@DDAESA10.BITNET (02/09/86)
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
I can see that a simple condition handler would let me do the dump OK
but the tricky bit would seem to be getting it in a format that the
debugger can handle.
Anyone got any suggestions????
------------ standard denial of everything ------ 00000010
any views expressed are purely my own and may not reflect those 00000100
of my employer - the European Space Agency 00000200
00000300
N. Head, ESC1111@DDAESA10, ESC1111%ESOC.BITNET 00000400
RobertBoschstr. 5 00000500
6100 Darmstadt 00000600
Federal Rep. Germany 00000700#D15@DDATHD21.BITNET (02/11/86)
Ref: ESC1111%DDAESA10.BITNET
Hallo,
I didn't read your original message, but it sounds that you should
enter:
$SET PROCESS/DUMP
before running your program and then analyze the .DMP file with
$ ANALYZE/PROCESS file.DMP
which is very similar to DEBUG.
With kind regards
Martin Knoblauch
Dept. for physical chemistry, PC 1
TH-Darmstadt, Petersenstr. 20, D6100 Darmstadt, West-Germany
BITNET: <#D15@DDATHD21.BITNET>