reexecuting a killed program

reexecuting a killed program

Post by William Sherman -Visualizati » Sat, 08 Dec 1990 00:31:03

I have two similar questions reguarding the reexecution of a program
whose state has been saved (core file or otherwise).  The reexecution
should start where the program left off, with all the variables and
memory intact.

Question 1:  Can (and how) one send a signal to a program causing
        a core dump that can later be run by rejoining the core with
        the executable (either through dbx or some other program).
        Are there any restrictions as to what a program can be in
        the process of doing when signaled?  I've tried sending
        a quit (signal 3), which produces a core dump, but dbx won't
        let me do a continue.

Question 2:  This one I know can be done, because Kyoto Common Lisp
        does it.  But after looking at the source, I wasn't able to
        decipher what was going on.  What I want is for a program
        to save itself, such that it creates an executable file which
        when run is basically in the same state as when saved.  KCL
        does this so that all the user data structures (and therefore
        functions) are exactly as they were.  In fact, the basic KCL
        executable has already had this done once.  So, to restate
        the problem: how does a program save itself into a file that
        simply needs to be executed for the user to be right back
        where he/she was when the program was saved.  (Note, actually
        terminating the program at this point is optional.)

/* Bill Sherman                                                         */
/* National Center for Supercomputing Applications                      */
/* University of Illinois                                               */
/* Champaign-Urbana                                                     */
/*                                                                      */

/*                                                                      */
/*   "You want to do mankind a real service?  Tell funnier jokes."    */
/*              Og                                                      */


reexecuting a killed program

Post by Heiko Blu » Sun, 09 Dec 1990 05:00:16

Quote:>I have two similar questions reguarding the reexecution of a program
>whose state has been saved (core file or otherwise).  The reexecution
>should start where the program left off, with all the variables and
>memory intact.

if you have the *unstripped* executable and the core file you
can use 'undump new.binary a.out.file core.file'. there is
a undump in the TeX distribution.

however i think you'll have trouble with programs using
curses etc, haven't tried, though.

                    public source archive [HST V.42bis]:
        scuzzy Any ACU,f 38400 6919520 gin:--gin: nuucp sword: nuucp
                     uucp scuzzy!/src/README /your/home


1. A program you CAN'T kill with kill -9

: Hello to all Linux programmers, or to those who know at least a bit more
: than I do about UNIX programming. I enclose a binary of a program at the
: end of this message, without the source, since the source wasn't given to
: me, because the guy who wrote it just doesn't want to give it to me(he
: thinks it's too cool of a program).

  What kind of idiots do you think we are? Running an unknown binary on my


  I would advise anyone seeing this post to NOT run it unless you really
know what you are doing!

 "Everyone is a prisoner holding their own key." |      (360)569-2911                  |   Electronics/uP files

2. extendfs - more questions

3. program killed with killed message.

4. How to set up a user account to use the mail's function only?

5. minimizing program kills the program!

6. Slackware 1.0.5 & SL/IP?


8. Dual Celeron systems - is there a reason the CPU box says for uniprocessor systems only

9. Kill COREL; Kill COREL; Kill COREL; ...

10. A method to kill process that cannot be killed even with `kill -9'.

11. How to kill process which not killed by 'kill' ?

12. Killing bugging programs...

13. program to kill process that's been runing for more than xx minutes