Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uunet!munnari!vuwcomp!frc!ncd
From: ncd@frc.UUCP (the nemesis)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: core dumps life-after-death
Message-ID: <276@frc.UUCP>
Date: Sun, 5-Jul-87 07:03:46 EDT
Article-I.D.: frc.276
Posted: Sun Jul  5 07:03:46 1987
Date-Received: Tue, 7-Jul-87 06:27:06 EDT
Distribution: comp
Organization: Fisheries Research, Ministry of Ag. and Fish., Wellington, N.Z.
Lines: 46
Keywords: resurrection life-after-death coredumps etc
Xref: mnetor comp.unix.questions:3104 comp.unix.wizards:3136

Ive found the that dbx utility great for examining
core dumps, ideal for finding importabilities in portable
ported code. What/why are the restriction on restarting
the coreimage as a process?

	I imagine there are problems with open files,
file positions, and other "kernel" type information.
Can a process get all this "stuff" as it dies. And 
do the tools to recreate the "old" environment already
exist?

	Can core Images be used to checkpoint large jobs?

	In a similiar blood vessel, On our Pyrimad (sysV+4.2BSD)
we have a selection of signals, ie ...
HUP INT QUIT ILL TRAP IOT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM 
STOP TSTP CONT CHLD TTIN TTOU TINT XCPU XFSZ 
However on microport(sysV) many of these dont exist. The ones
Id like are TSTP STOP CONT. How do you "stop"/suspend a process
in sysV?.

	And finally, how does one find out about "the kernal"
without having a source license? Are there any good books that I 
should be ordering? The kind of books that out line how to get
the best out of unix, and tricks of the trade etc...

Ive seen some good ones, like
	Advanced Unix Programming (Marc J. Rochkind) (great book!)
	The Minix book was great also, but its not Unix.	
	
	Just thought Id ask... 

	Neville

BTW. If only(and any) of the big boys can afford to have a 
Unix source license, I cannot see the logic in making the 
source so sacred. It just means that the little (and interested)
guys go without and have to wait for their hardware suppliers
to patch found(and annoying) bugs.
	What "could" be happening is the suppliers consider
the "temporary fixes" to be their "property" (gives them a
competitive edge and all that). And thus the users suffer.
Ive heard of cases (elsewhere) that this is concidered the case.

PERHAPS the answer is only big boys are worth suing....
WTB.