Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site arizona.UUCP Path: utzoo!watmath!clyde!burl!ulysses!harpo!utah-cs!arizona!budd From: budd@arizona.UUCP Newsgroups: net.unix-wizards Subject: generalized suspend wanted Message-ID: <8348@arizona.UUCP> Date: Mon, 27-Feb-84 15:11:20 EST Article-I.D.: arizona.8348 Posted: Mon Feb 27 15:11:20 1984 Date-Received: Tue, 28-Feb-84 13:06:08 EST Organization: CS Dept, U of Arizona, Tucson Lines: 19 The following problem seems conceptually easy, but subtle to implement - before I consider it further - has anybody else done anything similar? Generally speaking, the idea is to suspend a program and then pick it up later, even if later is across login boundaries (three weeks later, for example). The general solution would be to hack the shell to give you these capabilities. Slightly less bothersome would be to have some routine, eg, suspend_me, which when called produces a something and then gracefully dies. That something can somehow be started up again, acting as if suspend_me returned and all was normal. I originally thought suspend_me could produce a new a.out file, but it appears one cannot initialize the stack and registers with that approach. I believe suspend_me will have to produce a core dump, and to restart somethig will have to rummage through that core dump and set everything up. adb and sdb do this using ptrace, which would mean creating a child in the image that you would like, resetting the stack and malloc'ed areas one word at a time, starting the child and going away. - there must be an easier way. Anybody have any leads?