Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!prls!amdimage!amdcad!cae780!leadsv!rtgvax!ksh
From: ksh@rtgvax.UUCP (Kent S. Harris)
Newsgroups: net.unix-wizards
Subject: Re: restarting core images
Message-ID: <47@rtgvax.UUCP>
Date: Mon, 7-Apr-86 20:24:40 EST
Article-I.D.: rtgvax.47
Posted: Mon Apr  7 20:24:40 1986
Date-Received: Sat, 12-Apr-86 00:38:05 EST
References: <741@puff.UUCP>
Organization: Santa Clara Valley Computer Sciences, Cupertino, CA
Lines: 18
Keywords: core image, process migration, checkpointing

In article <741@puff.UUCP>, tom@puff.UUCP (Tom Christiansen) writes:
> OS:   BSD4.3 UNIX w/ Sun NFS
> CPU:  MicroVax II WorkStations, Vax 7[58]0's
> 
> Does anyone out there have any experience with restarting core images as
> generated either by the core() function ...

There is a simple program (sorry, I don't have it on the machine I'm
currently on but I can get you a copy if you ask me by E-mail) distributed
in the public domain by the folks that turn out the TeX distribution
tape (its called undump).  `Undump' takes an original a.out and a core
file (generated by abort() for example) and builds a new a.out image
with all of the original .text as .data.  Be advised, not all vendors
have remained true to the ZMAGIC (413) a.out format.  Sun (vax, etc) allocates
an entire UPAGE for the exec structure on  the front of 413 file, whereas ISI
allocates just the exec struct immediately followed by text segment (the text
size includes this header).  ISI should have cobbed up a new magic number
as there is nothing sacred with "413".