Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!mhuxr!mhuxn!ihnp4!ucbvax!info-vax
From: ESC1111@DDAESA10.BITNET
Newsgroups: mod.computers.vax
Subject: abort tracing
Message-ID: <8602082100.AA04361@ucbvax.berkeley.edu>
Date: Sat, 8-Feb-86 16:00:23 EST
Article-I.D.: ucbvax.8602082100.AA04361
Posted: Sat Feb  8 16:00:23 1986
Date-Received: Sun, 9-Feb-86 02:13:53 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 24
Approved: info-vax@sri-kl.arpa

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